Restart a queued pull request's tests
Requires the Merge and cancel PRs permission. Disruptive. Abandons the entry’s in-flight verification and starts a new one, discarding CI progress. Only possible while the entry is testing or in pending-failure; other live states are refused with PR_TESTS_NOT_RESTARTABLE.
This endpoint does not diagnose anything — to find out why an entry keeps being re-tested, read GET /v2/pull-requests/{id}/queue-entry-history and inspect each transition’s reason. Idempotency-Key is not yet honored, so a retry after a timeout starts a second restart; read the entry back instead of retrying. The request body is ignored.
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
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"