Skip to content

ci(mergify): upgrade configuration to current format (backport #48)#49

Merged
mergify[bot] merged 1 commit into
version-15-hotfixfrom
mergify/bp/version-15-hotfix/pr-48
May 22, 2026
Merged

ci(mergify): upgrade configuration to current format (backport #48)#49
mergify[bot] merged 1 commit into
version-15-hotfixfrom
mergify/bp/version-15-hotfix/pr-48

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented May 22, 2026

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-31, otherwise your configuration will stop working.

What's Changed?

  • The default value of merge_protections_settings.reporting_method is changing from check-runs to deployments. Your configuration has been updated to explicitly set check-runs to 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! 🎉


This is an automatic backport of pull request #48 done by Mergify.

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 22, 2026

Confidence Score: 5/5

Safe to merge — the change simply makes an implicit default explicit with no effect on the current workflow.

The two added lines lock in the existing check-runs reporting method rather than letting the Mergify platform silently switch to deployments. No merge rules, conditions, or actions are touched.

No files require special attention.

Important Files Changed

Filename Overview
.mergify.yml Adds merge_protections_settings.reporting_method: check-runs to explicitly preserve the current behavior before Mergify changes its default to deployments on 2026-07-31.

Reviews (1): Last reviewed commit: "ci(mergify): upgrade configuration to cu..." | Re-trigger Greptile

@mergify mergify Bot merged commit 4e27d22 into version-15-hotfix May 22, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants