Update the merge queue.
Authorizations
Body
The branch that the merge queue is targeting.
The desired state of the merge queue. Valid values: RUNNING, PAUSED, DRAINING.
running, paused, draining The number of PRs or batches of PRs the queue can test at once.
1 <= x <= 4294967295The number of tests the merge queue can run when bisecting a batch to figure out what PR in the batch failed.
1 <= x <= 4294967295The maximum number of minutes the merge queue will wait for tests to complete before timing out. Set to 0 to disable the timeout.
0 <= x <= 4294967295When enabled, PRs that fail tests will wait for the specified number of PRs below them to finish testing before getting kicked from the queue. This works best with optimistic merging enabled. Set to 0 to disable.
0 <= x <= 4294967295When enabled, a PR that passes tests will also cause any PR ahead of it in the queue to also get marked as passing, since tests have passed with those commits.
Enable or disable batching. When enabled, the merge queue will group PRs into batches for testing.
The maximum number of minutes the merge queue will wait to collect PRs into a batch before starting tests.
1 <= x <= 4294967295The minimum number of PRs required to form a batch.
1 <= x <= 4294967295The queue mode. 'single' processes PRs one at a time. 'parallel' processes multiple PRs concurrently.
single, parallel Whether or not Merge Queue will post GitHub comments on PRs.
Whether or not users are allowed to submit PRs to the merge queue by commenting /trunk merge.
Whether or not the merge queue will create PRs for its testing branches, allowing CI to run on them.
Allow PRs to merge directly into the target branch if they're up to date with the target branch when submitting them to the queue instead of running tests on them in the merge queue.
off, always The optimization strategy for the merge queue. 'off' disables optimizations. 'bisection_skip_redundant_tests' uses bisection and skips redundant tests.
off, bisection_skip_redundant_tests The Git merge method used when merging PRs into the target branch. Valid values: merge_commit, squash, rebase.
merge_commit, squash, rebase How the merge queue builds the branch CI runs on. Valid values: rename_temp_branch, push_new_branch_from_temp.
rename_temp_branch, push_new_branch_from_temp Post a GitHub status check on PRs with the status of the PR in the merge queue.
Whether the Trunk Merge Queue browser extension is enabled (shown) for this repository.
Allows setting the statuses that must pass when the merge queue performs tests in order for a PR to merge. Setting the statuses here will override GitHub branch protection settings or your .trunk/trunk.yaml.
Removes a manually specified set of required statuses. After this, the statuses that must pass when the merge queue performs testing will be pulled from either GitHub branch protection settings or your .trunk/trunk.yaml.
Sets the GitHub logins of bot/app accounts (e.g. dependabot[bot]) whose PRs are allowed to be submitted to the merge queue. This replaces the existing set. Pass an empty list to clear all allowed bot submitters.
Sets how PRs are batched based on the build targets they impact, for queues in parallel mode that upload impacted targets. This replaces the existing set of rules. Pass an empty list to clear all batching rules.
The GitHub label whose application enqueues a PR onto the merge queue.
1Whether 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.
The number of hours a PR can remain submitted but not mergeable before it is removed from the queue. Set to 0 to disable the timeout.
0 <= x <= 4294967295Response
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.