Skip to content

docs(merge-queue): document GITHUB_API_RATE_LIMIT_EXCEEDED failure reason#62

Open
samgutentag wants to merge 1 commit into
mainfrom
sam-gutentag/merge-queue-github-rate-limit-failure
Open

docs(merge-queue): document GITHUB_API_RATE_LIMIT_EXCEEDED failure reason#62
samgutentag wants to merge 1 commit into
mainfrom
sam-gutentag/merge-queue-github-rate-limit-failure

Conversation

@samgutentag
Copy link
Copy Markdown
Member

Summary

Trunk Merge Queue now surfaces a specific GITHUB_API_RATE_LIMIT_EXCEEDED failure reason when a PR is dropped because Trunk hit GitHub's API rate limit. This PR adds a failure reason reference table to the handle-failed-pull-requests page documenting what the error means and how to recover.

Source

Test plan

  • Check Mintlify preview link (posted on the PR by the Mintlify GitHub app)

Generated by Claude Code

…ason

Adds a failure reason reference table to the handle-failed-pull-requests
page and documents the new GITHUB_API_RATE_LIMIT_EXCEEDED reason with
what causes it and how to recover.

Source: trunk2 PR #4001

Co-Authored-By: Claude <noreply@anthropic.com>
@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented May 21, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
trunk 🟢 Ready View Preview May 21, 2026, 11:01 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Copy link
Copy Markdown
Member Author

Verification status (May 21, 2026): live

Verified: customers can use this. Ready to publish.

  • Eng PR: https://github.com/trunk-io/trunk2/pull/4001
  • Flag: none
  • Signals: Eng PR #4001 merged 2026-05-20T21:18:44Z. No feature flags found in diff. Change is a database migration (adds GITHUB_API_RATE_LIMIT_EXCEEDED to failure reason enum), effective immediately on merge.

No further action needed before publishing.


Generated by Claude Code

@samgutentag samgutentag marked this pull request as ready for review May 21, 2026 11:01
@samgutentag samgutentag added the ready to merge Verify docs PR: customers can use this. Ready to publish. label May 21, 2026 — with Claude
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready to merge Verify docs PR: customers can use this. Ready to publish.

Development

Successfully merging this pull request may close these issues.

2 participants