Reprioritize a queued pull request
Requires the Set priority on PRs permission. 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.
Changes a live queue entry’s priority. Exactly one of priorityValue or priorityName is required. priorityValue: 0 is the write path for skipping the line. The entry keeps its merge method. The pull request must have a non-terminal queue entry, or the call returns PR_NOT_IN_ACTIVE_STATE.
Idempotency-Key is not honored. If a request times out, read the pull request’s queue entry before retrying.
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
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"