Skip to content

ci(mergify): upgrade configuration to current format - #1490

Open
mergify[bot] wants to merge 6 commits into
mainfrom
mergify/configuration-deprecated-update
Open

mergify[bot] wants to merge 6 commits into
mainfrom
mergify/configuration-deprecated-update

Conversation

@mergify

@mergify mergify Bot commented May 1, 2026 •

Copy link
Copy Markdown
Contributor

Important

Enable Merge Protections for this repository and Mergify will migrate the deprecated fields below for you.
Once it migrates them, Mergify rebuilds this pull request's branch from your default branch and any commit pushed to it is replaced.

Hey there! 👋

We've noticed that your Mergify configuration is using some deprecated fields. Mergify can update them for you once Merge Protections is enabled for this repository:

  • queue_rules → autoqueue: autoqueue in queue_rules has been removed. A configuration that still sets it is rejected: use auto_merge_conditions in merge_protections_settings instead. (deadline: 2026-07-16)

Here is why Mergify waits on each one:

  • queue_rules → autoqueue in rule default: autoqueue no longer exists, so Mergify rejects this configuration while it still sets it. Its replacement, merge_protections_settings.auto_merge_conditions, only runs when the Merge Protections product is enabled: enable Merge Protections for this repository in the Mergify dashboard and Mergify will migrate autoqueue for you. Removing autoqueue by hand also gets Mergify running again, but pull requests then stop being queued automatically.

Do not procrastinate! You must upgrade your configuration before 2026-07-16, otherwise your configuration will stop working.

What should I do?

Enable Merge Protections for this repository in the Mergify dashboard. On its next pass, Mergify migrates these fields in this pull request, and you can review and merge it like any other.

If you fix your default branch another way, this pull request will close automatically once it no longer uses these fields.

Got Questions? We've Got Answers! 🙌

Why didn't Mergify migrate this for me?

The replacement for these fields only works with Merge Protections. Migrating them before it is enabled would stop them from working, so Mergify waits for it.

What if I run into issues or have concerns?

We're here to help! Feel free to reach out to our support team anytime.

Happy merging! 🎉

@netlify

netlify Bot commented May 1, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for cheerful-kitten-f556a0 canceled.

Name Link
🔨 Latest commit 0f630c5
🔍 Latest deploy log https://app.netlify.com/projects/cheerful-kitten-f556a0/deploys/6ad1fbd530b5f0752e26b720

@coderabbitai

coderabbitai Bot commented Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Repository: ambient-code/platform/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 8ec6dc82-faac-479d-a4ad-b138a6b24370

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@mergify
mergify Bot force-pushed the mergify/configuration-deprecated-update branch from f1b3e8c to 69b20ee Compare September 29, 2026 08:50

This branch has not been deployed

No deployments
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.

0 participants