ci(mergify): upgrade configuration to current format#289
Open
mergify[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
Merge Protections🔴 3 of 7 protections blocking · waiting on 👀 reviews and 🤖 CI
🔴 📃 Configuration Change RequirementsWaiting for
This rule is failing.Mergify configuration change
🔴 🤖 Continuous IntegrationWaiting for
This rule is failing.
🔴 👀 Review RequirementsWaiting for
This rule is failing.
Show 4 satisfied protections🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
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 still contains deprecated fields that Mergify could not migrate automatically.
This can happen when the deprecated fields live under a
sharedkey or behind YAML anchors — Mergify cannot know what these define, so it cannot modify them — or when a value has no automatic equivalent and needs a manual rewrite.In order for the configuration to be valid, you will need to manually modify it.
Here is the list of the remaining deprecated fields:
queue_rules → 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-09-30, otherwise your configuration will stop working.
What's Changed?
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)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! 🎉