docs(auto-merge): reading mergeStateStatus BLOCKED (required vs non-required)

[CybotTM]

From a 23-repo release sweep retro.

A red non-required check never blocks merge; BLOCKED usually means required checks are still pending. Real case: two PRs showed copilot-pull-request-reviewer = failure (quota-exhausted) but it was not in required_status_checks, so both auto-merged once the required set went green. Adds how to list the required set and the corollary not to reach for --admin.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Code Review

This pull request updates the auto-merge guide documentation to add a new section explaining the mergeStateStatus: BLOCKED status. It clarifies that a BLOCKED status often indicates pending required checks rather than a failure, and highlights that failing non-required checks do not prevent auto-merging. There are no review comments, so I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.