Skip to content

docs: GitHub rate limit FAQ + Linear required-at-creation fields#64

Open
samgutentag wants to merge 1 commit into
mainfrom
sam-gutentag/merge-queue-rate-limit-and-required-fields
Open

docs: GitHub rate limit FAQ + Linear required-at-creation fields#64
samgutentag wants to merge 1 commit into
mainfrom
sam-gutentag/merge-queue-rate-limit-and-required-fields

Conversation

@samgutentag
Copy link
Copy Markdown
Member

Summary

  • Merge Queue FAQ: adds an accordion explaining the GitHub API rate limit exceeded failure reason so users know what causes it and how to recover (trunk2 PR #4016)
  • Flaky Tests / Linear integration: documents the "Require user to fill at creation" option for field defaults, which enforces required fields in the Create Ticket modal (trunk2 PR #4011)

Source

  • trunk2 PR #4016: Add github rate limit exceeded failure reason proto
  • trunk2 PR #4011: fix: enforce 'require at creation' fields in create ticket modal

Test plan

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

Generated by Claude Code

… fields

- Merge Queue FAQ: new accordion explaining the GitHub API rate limit
  exceeded failure reason (trunk2 #4016)
- Linear ticketing: document the Require user to fill at creation option
  for field defaults (trunk2 #4011)

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

mintlify Bot commented May 22, 2026

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

Project Status Preview Updated (UTC)
trunk 🟢 Ready View Preview May 22, 2026, 4:54 PM

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

Copy link
Copy Markdown
Member Author

Verification status (May 22, 2026): live

Verified: customers can use this. Ready to publish.

  • Eng PRs: trunk-io/trunk2#4016, trunk-io/trunk2#4011
  • Flag: none
  • Signals: Both PRs squash-merged to trunk2 main on 2026-05-22. No feature flags found in diffs. Proto addition and bug fix ship on merge.

Re-run /verify-docs-pr if the scope of this PR changes.


Generated by Claude Code

@samgutentag samgutentag marked this pull request as ready for review May 22, 2026 16:54
@samgutentag samgutentag added the ready to merge Verify docs PR: customers can use this. Ready to publish. label May 22, 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