| description | Verify your Trunk Merge Queue installation by submitting a test PR and confirming it merges automatically. |
|---|
After completing configuration, verify your setup:
-
trunk-iobot is added to push restrictions for your protected branch - No branch protection rules apply to
trunk-temp/*ortrunk-merge/*branches - If using Draft PR mode: Required status checks are configured in GitHub branch protection
- If using Push-triggered mode:
- CI workflows trigger on
trunk-merge/**branches -
merge.required_statusesis defined intrunk.yaml
- CI workflows trigger on
- Create a test pull request
- Comment
/trunk mergeon the pull request - Check the Trunk Dashboard to monitor your pull request status
- The pull request should appear in the queue as "Queued" until all checks complete
- Click on the pull request in the dashboard to see detailed status of what it's waiting for
- You'll also see status updates in the comments on your pull request
Expected behavior: Your pull request should progress through testing and merge automatically once all required checks pass.
π Congratulations! Your Merge Queue is working. You're ready to use it with your team.
β Submit and cancel pull requests - Learn how to use the queue day-to-day
Ready to make it even better? Explore these optimizations
β Predictive Testing - Prevent queue collapse and increase throughput
β Batching - Merge multiple PRs together for faster processing
β Priority merging - Fast-track urgent PRs
β Anti-flake protection - Handle flaky tests automatically
β Integration for Slack - Get notifications in Slack
β Metrics and monitoring - Track your queue's performance
Having trouble? See our Troubleshooting guide for common installation issues.