ci(mergify): upgrade configuration to current format - #1312
Closed
mergify[bot] wants to merge 1 commit into
Closed
Conversation
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
17 times, most recently
from
April 24, 2026 09:37
e436b4c to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
April 24, 2026 11:24
74e5c30 to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
10 times, most recently
from
April 27, 2026 13:27
6e669d4 to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
April 28, 2026 11:30
98191c5 to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
April 28, 2026 12:29
fa027d9 to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
5 times, most recently
from
April 29, 2026 07:16
931bbb0 to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
April 29, 2026 11:59
896f4bc to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
2 times, most recently
from
April 29, 2026 12:24
d612c17 to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
April 29, 2026 12:40
381a551 to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
4 times, most recently
from
April 29, 2026 14:10
4ed7fb2 to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
April 29, 2026 15:35
4f4aef9 to
c75753d
Compare
mergify
Bot
force-pushed
the
mergify/configuration-deprecated-update
branch
3 times, most recently
from
April 30, 2026 10:53
3909b77 to
c75753d
Compare
|
This pull request is now marked as stale because it hasn't seen activity for a while. Add a comment or it will be closed soon. |
|
Closing this pull request as it hasn't seen activity for a while. Please add a comment @mentioning a maintainer to reopen. |
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
The transformed Mergify configuration is invalid or contains deprecated fields that should have been transformed.
The
sharedkey in your configuration could be the cause, Mergify cannot know what is inside thissharedkey so it cannot modify it.In order for the configuration to be valid, you will need to manually modify it.
Here is the list of the remaining deprecated fields:
pull_request_rules → actions → queue → methodpull_request_rules → actions → queue → commit_message_templateHey 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?
pull_request_rules → actions → delete_head_branch: Thedelete_head_branchaction is deprecated. Use GitHub's native 'Automatically delete head branches' setting instead: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches (deadline: 2026-07-31)queue_rules → conditions:conditionsin queue rule configuration is deprecated. Usemerge_conditionsinstead. (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! 🎉