Repository navigation
ci(mergify): upgrade configuration to current format - #1490
Open
mergify[bot] wants to merge 1 commit into
Open
mergify[bot] wants to merge 1 commit into
mergify[bot] wants to merge 1 commit into
Conversation
✅ Deploy Preview for cheerful-kitten-f556a0 canceled.
|
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
September 29, 2026 08:50
f1b3e8c to
69b20ee
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
October 30, 2026 13:50
0f630c5 to
1b09eb4
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.
Note
Merge Protections is not enabled for this repository.
The settings this PR writes for it stay inactive until you enable Merge Protections.
Mergify no longer accepts the syntax they replace, so you don't need Merge Protections to merge this PR.
Important
Mergify manages this pull request's branch. Each time a change on your default branch, or a new migration, changes what this pull request should contain, the branch is rebuilt from your default branch and any commit pushed to it is replaced.
Make your own changes in a separate pull request against your default branch instead.
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-16, otherwise your configuration will stop working.
What's Changed?
queue_rules → autoqueue:autoqueueinqueue_ruleshas been removed. A configuration that still sets it is rejected: useauto_merge_conditionsinmerge_protections_settingsinstead. (deadline: 2026-07-16)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?
Yes! You don't need to enable the product named at the top of this description to merge it: the settings that need it stay inactive until you do.
Do I need to do anything special after merging?
Yes — enable the product named at the top of this description to turn on the settings that need it, then you're all set. It's also a good idea to give any custom configurations 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! 🎉