Skip to content

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

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

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

Conversation

@mergify

@mergify mergify Bot commented Apr 24, 2026

Copy link
Copy Markdown

Caution

The transformed Mergify configuration is invalid or contains deprecated fields that should have been transformed.
The shared key in your configuration could be the cause, Mergify cannot know what is inside this shared key so it cannot modify it.
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_template
  • queue_rules → commit_message_template
  • queue_rules → commit_message_template

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)

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! 🎉

@sourcery-ai

sourcery-ai Bot commented Apr 24, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Mergify CI configuration to the current format by explicitly preserving previous high-priority queue behavior regarding check interruption.

Flow diagram for Mergify priority rule with allow_checks_interruption enabled

flowchart TD
  A[Pull request updated] --> B[Evaluate Mergify priority_rules]
  B --> C{Matches label priority:high?}
  C -->|No| D[Evaluate other rules or use default priority]
  C -->|Yes| E[Assign priority high]
  E --> F[Apply allow_checks_interruption true]
  F --> G{Are required checks still running?}
  G -->|No| H[Proceed with normal merge/queue behavior]
  G -->|Yes| I[Allow interruption of running checks for high priority]
  I --> J[Reorder PR in queue based on high priority]
  J --> K[Trigger merge when conditions are satisfied]
Loading

File-Level Changes

Change Details Files
Explicitly set high-priority rule to allow interrupting running checks to preserve legacy behavior under new Mergify defaults.
  • Add allow_checks_interruption: true to the high-priority entry in priority_rules
  • Keep all other Mergify configuration and queue_rules unchanged to maintain existing workflows
.mergify.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@mergify mergify Bot force-pushed the mergify/configuration-deprecated-update branch from ede0561 to fc9363e Compare April 24, 2026 08:54
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