Repository navigation
ci(mergify): upgrade configuration to current format - #1490
Open
mergify[bot] wants to merge 6 commits into
Open
mergify[bot] wants to merge 6 commits into
mergify[bot] wants to merge 6 commits into
Conversation
✅ Deploy Preview for cheerful-kitten-f556a0 canceled.
|
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
September 29, 2026 08:50
f1b3e8c to
69b20ee
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Important
Enable Merge Protections for this repository and Mergify will migrate the deprecated fields below for you.
Once it migrates them, Mergify rebuilds this pull request's branch from your default branch and any commit pushed to it is replaced.
Hey there! 👋
We've noticed that your Mergify configuration is using some deprecated fields. Mergify can update them for you once Merge Protections is enabled for this repository:
queue_rules → autoqueue:autoqueueinqueue_ruleshas been removed. A configuration that still sets it is rejected: useauto_merge_conditionsinmerge_protections_settingsinstead. (deadline: 2026-07-16)Here is why Mergify waits on each one:
queue_rules → autoqueuein ruledefault:autoqueueno longer exists, so Mergify rejects this configuration while it still sets it. Its replacement,merge_protections_settings.auto_merge_conditions, only runs when the Merge Protections product is enabled: enable Merge Protections for this repository in the Mergify dashboard and Mergify will migrateautoqueuefor you. Removingautoqueueby hand also gets Mergify running again, but pull requests then stop being queued automatically.Do not procrastinate! You must upgrade your configuration before 2026-07-16, otherwise your configuration will stop working.
What should I do?
Enable Merge Protections for this repository in the Mergify dashboard. On its next pass, Mergify migrates these fields in this pull request, and you can review and merge it like any other.
If you fix your default branch another way, this pull request will close automatically once it no longer uses these fields.
Got Questions? We've Got Answers! 🙌
Why didn't Mergify migrate this for me?
The replacement for these fields only works with Merge Protections. Migrating them before it is enabled would stop them from working, so Mergify waits for it.
What if I run into issues or have concerns?
We're here to help! Feel free to reach out to our support team anytime.
Happy merging! 🎉