Skip to content

[ready to merge] docs(merge-queue): document label-based PR enqueueing#30

Draft
samgutentag wants to merge 1 commit into
mainfrom
sam-gutentag/mq-enqueue-by-label
Draft

[ready to merge] docs(merge-queue): document label-based PR enqueueing#30
samgutentag wants to merge 1 commit into
mainfrom
sam-gutentag/mq-enqueue-by-label

Conversation

@samgutentag
Copy link
Copy Markdown
Member

Summary

  • Adds an Enqueueing by label section to the Submit and cancel pull requests reference page
  • Documents how to configure a GitHub label to auto-enqueue PRs, the trigger behavior, and cancellation caveats

Source

Test plan

  • Check Mintlify preview link (posted on the PR by the Mintlify GitHub app)
  • Verify the new section renders under "Submitting and cancelling pull requests"
  • Verify the Info callout renders correctly

Generated by Claude Code

Add an Enqueueing by label section to the submit/cancel reference page,
covering how to configure the GitHub label, the auto-enqueue trigger
behavior, and cancellation caveats.

Tracks trunk2 PR: https://github.com/trunk-io/trunk2/pull/3956
Linear: https://linear.app/trunk/issue/TRUNK-18344

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

mintlify Bot commented May 18, 2026

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

Project Status Preview Updated (UTC)
trunk 🟢 Ready View Preview May 18, 2026, 10:49 PM

@samgutentag samgutentag changed the title docs(merge-queue): document label-based PR enqueueing [ready to merge] docs(merge-queue): document label-based PR enqueueing May 19, 2026
@samgutentag
Copy link
Copy Markdown
Member Author

Verification status (2026-05-19): live

Verified: customers can use this. Ready to publish.

  • Eng PR: trunk2#3956 (merged 2026-05-13)
  • Flag: none (feature gated by per-repo labelCommandsEnabled user setting; no LaunchDarkly flag)
  • Signals: feature is a user-configurable per-repo setting. Merged 6 days ago. Linked Linear: TRUNK-18344.

Note: per Phil's note in trunk2#3956 ("we can hold off on a public release until I get back"), confirm with Phil whether the broader launch comms are scheduled before publishing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants