ci(mergify): upgrade configuration to current format#620
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Coverage variation | Report missing for c6ed69f1 |
| Diff coverage | ✅ ∅ diff coverage |
Coverage variation details
Coverable lines Covered lines Coverage Common ancestor commit (c6ed69f) Report Missing Report Missing Report Missing Head commit (39a65ce) 567 394 69.49% Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch:
<coverage of head commit> - <coverage of common ancestor commit>
Diff coverage details
Coverable lines Covered lines Diff coverage Pull request (#620) 0 0 ∅ (not applicable) Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified:
<covered lines added or modified>/<coverable lines added or modified> * 100%
1 Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
Merge ProtectionsYour pull request matches the following merge protections and will not be merged until they are valid. 🟢 📃 Configuration Change RequirementsWonderful, this rule succeeded.Mergify configuration change
|
86655f6 to
c6ed69f
Compare
|
This pull request has been automatically marked as stale because it has been open for 30 days with no activity. If this PR is still being worked on, please:
This PR will be closed automatically in 7 days if no further activity occurs. |
|
This pull request was automatically closed because it has been stale for 7 days with no activity. If you want to continue working on this PR, please:
Thank you for your contributions! 🙏 |
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-01, otherwise your configuration will stop working.
What's Changed?
allow_checks_interruptionin priority rules is changing fromtruetofalse. Priority rules with a priority higher thanmediumthat rely on the default now needallow_checks_interruptionset explicitly totrueto preserve the previous behavior. (deadline: 2026-07-01)merge_protections_settings.reporting_methodis changing fromcheck-runstodeployments. Your configuration has been updated to explicitly setcheck-runsto preserve current behavior. (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! 🎉