Get the merge queue.
Authorizations
Response
OK
The state of the merge queue. See https://docs.trunk.io/merge-queue/administration/advanced-settings#merge-queue-state for the full description of each state.
running, paused, draining, switching_modes single, parallel Whether the Trunk Merge Queue browser extension is enabled (shown) for this repository.
The GitHub logins of bot/app accounts (e.g. dependabot[bot]) whose PRs are allowed to be submitted to the merge queue.
Rules changing how PRs are batched based on the build targets they impact.
Controls whether PRs can skip the queue's test run and merge directly when already up to date with the target branch. See https://docs.trunk.io/merge-queue/administration/advanced-settings#direct-merge-to-main for details.
off, always The optimization strategy for the merge queue. off — no optimizations. See https://docs.trunk.io/merge-queue/optimizations/batching#test-caching-during-bisection for details on bisection_skip_redundant_tests.
off, bisection_skip_redundant_tests The Git strategy used to merge a PR into the target branch. See https://docs.trunk.io/merge-queue/administration/advanced-settings#merge-method for details.
merge_commit, squash, rebase How the merge queue turns its built temporary branch into the trunk-merge branch CI runs on. rename_temp_branch renames the ref. push_new_branch_from_temp creates the final ref at the temporary branch's head commit and deletes the temporary ref, which needs no rename permission — use it when an organization- or enterprise-level ruleset targets these branches, since GitHub's rename restriction is the one rule an exempt bypass actor cannot lift.
rename_temp_branch, push_new_branch_from_temp The GitHub label whose application enqueues a PR onto the merge queue.
Whether label-based commands (e.g. enqueue/dequeue via labels) are enabled on the merge queue.
Whether the merge queue applies labels to PRs reflecting their merge queue state.