ci(mergify): upgrade configuration to current format #10921
Merged
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
|
Is it me, or did they just resend this without checking whether the first one was handled? |
mergify
bot
force-pushed
the
mergify/configuration-deprecated-update
branch
from
fc62937 to
72044fc
Compare
|
Wow, they insist... |
|
And they (a) again ignored the squash-merge queue (b) broke the bump direct PRs on release branches are supposed to get. I hopefully patched it up in a way their dumb bot will accept. |
ulysses4ever
approved these changes
Apr 30, 2025
|
So what's the status here? Do we close? |
ulysses4ever
force-pushed
the
mergify/configuration-deprecated-update
branch
from
f2258a7 to
931d65b
Compare
|
@Mikolaj it needs a second approval, and then it's good to go. If you try to close it, they will automatically reopen it (see above). |
geekosaur
approved these changes
May 8, 2025
mergify
bot
added
the
merge delay passed
ulysses4ever
force-pushed
the
mergify/configuration-deprecated-update
branch
from
931d65b to
d602ab7
Compare
mergify
bot
added
the
ready and waiting
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.
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 2025-06-30, otherwise your configuration will stop working.
What's Changed?
priority_rules.This transformation aim to create priority rules, based on your existing queue rules, in order to keep the same priorities. If this priority change is not needed for you, you should not close this pull request until the deadline, otherwise it will be re-created again. (deadline: 2025-06-30)
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! 🎉