Repository navigation
ci(mergify): upgrade configuration to current format - #285
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
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.
Caution
Your Mergify configuration uses deprecated fields that Mergify cannot migrate automatically.
Mergify did not change your configuration here: push your fix to this pull request.
Hey there! 👋
We've noticed that your Mergify configuration is using some deprecated fields. Mergify usually updates them for you automatically, but these ones have no exact automatic replacement — migrating them could change how your rules behave, so they need your judgment:
queue_rules → autoqueue:autoqueueinqueue_rulesis deprecated. Useauto_merge_conditionsinmerge_protections_settingsinstead. (deadline: 2026-07-16)queue_rules → commit_message_template: Thecommit_message_templatesetting is deprecated. Use the declarativecommit_message_formatinstead: https://docs.mergify.com/workflow/actions/merge#migrating-from-commit_message_template (deadline: 2026-09-30)Here is what stopped Mergify on each one:
queue_rules → autoqueuein rulemain: 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 migrateautoqueue; moving it by hand before that stops pull requests from being queued automatically.queue_rules → commit_message_templatein rulemain: This template has no exactcommit_message_formatequivalent. Rewrite it by hand.Do not procrastinate! You must upgrade your configuration before 2026-07-16, otherwise your configuration will stop working.
What should I do?
Update the fields listed above in your configuration file, following the documentation linked in each item, and push that change to this pull request's branch. As long as Mergify has nothing to migrate for you, it keeps the commits you push here, so you can review and merge the fix like any other pull request.
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 new syntax cannot reproduce your current configuration exactly. Rather than risk changing your workflows' behavior, we leave the migration to you.
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! 🎉