Repository navigation
ci(mergify): upgrade configuration to current format - #15
mergify[bot] wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Tick the box to add this pull request to the merge queue (same as
|
ab6d39d to
96a7b80
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
|
Tick the box to add this pull request to the merge queue (same as
|
|
Tick the box to add this pull request to the merge queue (same as
|
1 similar comment
|
Tick the box to add this pull request to the merge queue (same as
|
96a7b80 to
3e79988
Compare
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! 🎉