Skip to content

ci(mergify): upgrade configuration to current format#358

Merged
twisti-dev merged 2 commits intomasterfrom
mergify/configuration-deprecated-update
Apr 10, 2026
Merged

ci(mergify): upgrade configuration to current format#358
twisti-dev merged 2 commits intomasterfrom
mergify/configuration-deprecated-update

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 9, 2026

Hey there! 👋

We've noticed that your Mergify configuration is using some deprecated fields.

No worries—we've got your back! This automated PR updates your config to align with the newest standards, ensuring everything keeps running smoothly.

Do not procrastinate! You must upgrade your configuration before 2026-07-31, otherwise your configuration will stop working.

What's Changed?

  • The default value of merge_protections_settings.reporting_method is changing from check-runs to deployments. Your configuration has been updated to explicitly set check-runs to preserve current behavior. (deadline: 2026-07-31)

Why This Matters

Keeping your configuration up-to-date means you'll benefit from the latest features and improvements Mergify has to offer. Plus, it helps prevent any unexpected hiccups down the road.

Got Questions? We've Got Answers! 🙌

Is this update safe to merge?

Absolutely! We've made sure the changes are compatible with your current setup. Your workflows should continue to work just as before—if not better!

Do I need to do anything special after merging?

Nope! Just merge this PR, and you're all set. If you have any custom configurations, it's a good idea to give them a quick look to ensure everything's in order.

What if I run into issues or have concerns?

We're here to help! Feel free to reach out to our support team anytime.

Thanks for being awesome and keeping your configuration up-to-date! If you have any thoughts or need a hand, don't hesitate to let us know.

Happy merging! 🎉

@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented Apr 9, 2026

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 📃 Configuration Change Requirements

Wonderful, this rule succeeded.

Mergify configuration change

  • check-success = Configuration changed

@twisti-dev
Copy link
Copy Markdown
Collaborator

@Mergifyio queue

@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented Apr 10, 2026

Merge Queue Status

  • 🟠 Waiting for queue conditions
  • ⏳ Enter queue
  • ⏳ Run checks
  • ⏳ Merge

Waiting for:

  • -closed
  • any of:
    • check-neutral = build
    • check-skipped = build
    • check-success = build
  • any of:
    • check-neutral = test
    • check-skipped = test
    • check-success = test
All conditions
  • -closed [📌 queue requirement]
  • any of [🔀 queue conditions]:
    • all of [📌 queue conditions of queue rule default]:
      • any of [🛡 GitHub repository ruleset rule Default]:
        • check-neutral = build
        • check-skipped = build
        • check-success = build
      • any of [🛡 GitHub repository ruleset rule Default]:
        • check-neutral = test
        • check-skipped = test
        • check-success = test
      • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule Default]
      • #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule Default]
      • #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule Default]
      • any of [🛡 GitHub repository ruleset rule Default]:
        • check-success = Mergify Merge Protections
        • check-neutral = Mergify Merge Protections
        • check-skipped = Mergify Merge Protections
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of [📌 queue -> configuration change requirements]:
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of [📌 queue requirement]:
    • check-success = Mergify Merge Protections
    • check-neutral = Mergify Merge Protections
    • check-skipped = Mergify Merge Protections

@twisti-dev twisti-dev merged commit cb21d11 into master Apr 10, 2026
6 checks passed
@twisti-dev twisti-dev deleted the mergify/configuration-deprecated-update branch April 10, 2026 22:07
@github-project-automation github-project-automation Bot moved this from Backlog to Done in community-server-docs Apr 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant