Skip to content

docs: note auto-merge is enabled for the merge queue - #6

Open
joalves wants to merge 1 commit into
mainfrom
docs/enable-auto-merge
Open

joalves wants to merge 1 commit into
mainfrom
docs/enable-auto-merge

Conversation

@joalves

@joalves joalves commented Sep 29, 2026 •

Copy link
Copy Markdown
Collaborator

Repo-level auto-merge is now enabled, so gh pr merge --auto --squash <n> queues a PR into the merge queue. Updates CLAUDE.md, which said auto-merge was disabled. The GraphQL enqueue stays as a fallback.

Summary by CodeRabbit

  • Documentation
    • Updated merge guidance to reflect the required merge queue and enabled auto-merge. Contributors are instructed to queue pull requests after checks pass, with an alternative method if the usual command fails.

@coderabbitai

coderabbitai Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 19ebaee3-163d-4dcd-bc32-ae483c18c5ac

📥 Commits

Reviewing files that changed from the base of the PR and between 529196d and 9821e23.

📒 Files selected for processing (1)
  • CLAUDE.md

Included review availability: This review used your included allowance. 1 included review remains after this review. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.


Walkthrough

The release guidance now says that repository-level auto-merge is enabled. It instructs contributors to queue a pull request with gh pr merge --auto --squash <n> and use GraphQL if the command fails.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 9821e

The documented routes are consistent with the required merge queue on main; no actionable issue blocking merge was established.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: documenting that auto-merge is enabled for the merge queue.
Docstring Coverage ✅ Passed 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 ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

A rabbit read the queueing guide,
Then tucked the merge command inside.
When checks turn green, the queue takes flight,
GraphQL waits if commands balk tonight.
The burrow hums; the patch is right!

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant