Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: Mergifyio/gha-changelog-syncer
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main@{1day}
Choose a base ref
...
head repository: Mergifyio/gha-changelog-syncer
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
  • 1 commit
  • 1 file changed
  • 1 contributor

Commits on Mar 7, 2025

  1. ci(mergify): upgrade configuration to current format (#50) 

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

## What's Changed?

- `queue_rules → disallow_checks_interruption_from_queues`: This attribute has been replaced in favor of using `priority_rules` at the top-level of the configuration combined with the `allow_checks_interruption` key, also in the `priority_rules`.
:warning: The transformed configuration simply removes the deprecated attribute. We recommend you to create the required priority rules, if needed, to replace this deprecated attribute to fit properly to your merge queue's behavior. (deadline: 2025-05-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](mailto:support@mergify.com) 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! 🎉
    @mergify
    mergify[bot] authored Mar 7, 2025
    Copy the full SHA
    392bda0 View commit details

This comparison is taking too long to generate.

Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.

You can try running this command locally to see the comparison on your machine:
git diff main@{1day}...main