Skip to content

ci(mergify): upgrade configuration to current format#620

Open
mergify[bot] wants to merge 1 commit into
masterfrom
mergify/configuration-deprecated-update
Open

ci(mergify): upgrade configuration to current format#620
mergify[bot] wants to merge 1 commit into
masterfrom
mergify/configuration-deprecated-update

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Apr 4, 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-01, otherwise your configuration will stop working.

What's Changed?

  • The default value of allow_checks_interruption in priority rules is changing from true to false. Priority rules with a priority higher than medium that rely on the default now need allow_checks_interruption set explicitly to true to preserve the previous behavior. (deadline: 2026-07-01)
  • 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! 🎉

@codacy-production
Copy link
Copy Markdown

codacy-production Bot commented Apr 4, 2026

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Coverage ∅ diff coverage

Metric Results
Coverage variation Report missing for c6ed69f1
Diff coverage diff coverage

View coverage diff in Codacy

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.

@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented Apr 4, 2026

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 📃 Configuration Change Requirements

Wonderful, this rule succeeded.

Mergify configuration change

  • check-success = Configuration changed

@mergify mergify Bot force-pushed the mergify/configuration-deprecated-update branch from 86655f6 to c6ed69f Compare April 16, 2026 07:21
@github-actions
Copy link
Copy Markdown

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:

  • Add a comment to remove the stale label
  • Push new commits or updates
  • Request review if ready

This PR will be closed automatically in 7 days if no further activity occurs.
Thank you for your contributions! 🙏

@github-actions github-actions Bot added the Stale label May 17, 2026
@github-actions
Copy link
Copy Markdown

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:

  • Reopen the pull request
  • Address any feedback or conflicts
  • Remove the stale label

Thank you for your contributions! 🙏

@github-actions github-actions Bot closed this May 24, 2026
@mergify mergify Bot reopened this May 24, 2026
@github-actions github-actions Bot removed the Stale label May 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant