[jsell-rh]

What

Removes the autoqueue: true key from the default queue rule in .mergify.yml.

Why

Mergify is reporting the configuration as invalid and refuses to read the queue:

Extra inputs are not permitted @ root -> queue_rules -> item 0 -> autoqueue

autoqueue is not a valid key on a queue_rules item in the current Mergify schema (valid keys include name, queue_conditions, merge_conditions, merge_method, batch_size, ...). Automatic queueing is instead expressed via the queue action in pull_request_rules, which this config already has:

  - name: queue PRs when CI passes
    conditions:
      - -draft
      - -conflict
    actions:
      queue:
        name: default

So removing the deprecated key preserves the existing auto-queue behavior while making the configuration valid again. merge_method: squash is a valid queue_rules key and is kept.

Note: #1490 (the Mergify auto-generated "upgrade configuration" PR) does not fix this; its diff is only a file-mode change, leaving the invalid autoqueue key in place.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Behavior Changes
  • Changes are no longer automatically added to the merge queue by default. The existing squash merge method and queue conditions are unchanged.

[netlify]

✅ Deploy Preview for cheerful-kitten-f556a0 canceled.

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Source mode: Auto
• Repository: ambient-code/platform
• Branch: main
• File: .coderabbit.yaml
• Commit: 6e10db2
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Enterprise
• Run ID: 8281029f-062c-4a72-ae05-097b1a4bc279

📥 Commits

Reviewing files that changed from the base of the PR and between 6e10db2 and cae0ef6.

📒 Files selected for processing: 1

• .mergify.yml

💤 Files with no reviewable changes: 1

• .mergify.yml

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

📝 Walkthrough

The default Mergify queue rule no longer sets autoqueue: true. Its squash merge method and queue conditions remain unchanged.

Changes: Default Queue Rule

Layer / File(s)	Summary
Update the default queue rule .mergify.yml	The rule no longer sets autoqueue: true. Its squash merge method and queue conditions remain unchanged.

Priority: ⬇️ Low

Change: Bug fix

Merge Risk: ⚪ Minimal · up to cae0e

The existing queue configuration remains in place, with no identified change that would block merging.

Pre-merge checks: 8

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title follows Conventional Commits format and accurately describes removal of the invalid Mergify key.
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Performance And Algorithmic Complexity		PASS. The pull request changes only .mergify.yml and removes one invalid autoqueue configuration key. It introduces no algorithms, loops, API calls, list operations, storage, or frontend rendering…
Security And Secret Handling		PASSED. The PR changes only .mergify.yml and removes one configuration key. It adds no secrets, endpoints, service-account usage, injection paths, sensitive logging, or Kubernetes Secret resources. …
Kubernetes Resource Safety		PASS. The pull request changes only .mergify.yml and removes one Mergify key. It adds or changes no Kubernetes resources, containers, RBAC, namespaces, or pod security contexts.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files.

Full details: Performance And Algorithmic Complexity

Explanation

PASS. The pull request changes only .mergify.yml and removes one invalid autoqueue configuration key. It introduces no algorithms, loops, API calls, list operations, storage, or frontend rendering changes. No performance regression condition applies.

Full details: Security And Secret Handling

Explanation

PASSED. The PR changes only .mergify.yml and removes one configuration key. It adds no secrets, endpoints, service-account usage, injection paths, sensitive logging, or Kubernetes Secret resources. The remaining queue action and conditions contain no sensitive data.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

✨ Simplify code

• Commit to this branch
• Create a new PR

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