Update a queued pull request's entry
Requires Set priority on PRs to send priorityValue or priorityName, Skip batching to send allowBatching, Merge PRs with direct to queue to send direct, and Merge and cancel PRs to send mergeMethod. Lower priorityValue numbers go first, from 0 to 255. The named priorities are urgent (0), high (10), medium (100, the default), and low (200). Raising an entry that is already queued doesn’t restart anything: the new priority applies the next time the entry is placed in the queue. An entry still notReady set to urgent restarts lower-priority entries already testing when it enters the queue.
Patches a live queue entry; an omitted field leaves that attribute unchanged. priorityValue and priorityName are mutually exclusive. skipsTheLine is not settable — it is derived from priorityValue === 0, so send that instead. direct sends the entry directly to the queue past unmet readiness (it needs the Merge PRs with direct to queue permission, and a signed-in user also needs repository-admin permission). allowBatching: false gives the entry a test run of its own. mergeMethod chooses how this pull request is merged, and null returns it to the queue’s merge method.
Authorizations
An API key, sent as Authorization: Bearer <key>. An organization admin creates one in the Trunk app under Settings → Developer → API Keys and chooses the permissions it holds. A new key starts with no permissions: it can read merge queues but change nothing in them, and it cannot get a Dynamic CI plan. Each endpoint that needs a permission names it in its description; the Dynamic CI plan endpoints need Generate Dynamic CI plans.
Path Parameters
Body
Patches one or more attributes of a live queue entry; at least one must be sent. priorityValue and priorityName are mutually exclusive. skipsTheLine is not accepted — it is derived from priorityValue === 0, so send that. An omitted field leaves that attribute of the entry unchanged.
Send the pull request directly to the queue past unmet readiness (branch protection, failing required checks), merging via Trunk's bypass app. It does not skip the queue's own tests. It needs the Merge PRs with direct to queue permission, and a signed-in user also needs repository-admin permission. false clears it. Reflected as QueueEntry.direct.
false
How to merge this pull request: one of mergeCommit, squash, or rebase (see the MergeMethod schema). null clears it, so the queue's merge method applies. Omit to leave it unchanged. Sending this field at all needs the Merge and cancel PRs permission. A change is refused with PR_NOT_ENQUEUEABLE unless the queue lets pull requests choose their own merge method, while the pull request is being merged, and when the branch's rules forbid the method or the repository's provider does not support it.
mergeCommit, squash, rebase "rebase"
Response
The updated pull request
A pull request Trunk has indexed. There is no nested repository object — resolve repositoryId with GET /v2/repositories/{id}.
The head commit of the pull request as Trunk last indexed it. Compare against a verification run's testedPullRequests[].sha to tell whether a run tested the current head or a superseded one — a mismatch means the branch moved after that run started.
"9c58bf40e5c1a2b3d4e5f60718293a4b5c6d7e8f"