Skip to main content

Reliability

Every job runs. The action is built to retry for resiliency, but if Trunk is down, the action will fail open and all your jobs will run.
It uploads your pipeline unchanged, so every step runs.
It runs. A job needs a couple of days of history before Trunk will recommend skipping it.
Only when a paths filter you configured excludes it. See Merge queues.
Yes. Set the job to Run Before Queue. Trunk starts it on the head commit before the pull request enters the queue, unless it already ran there.
Trunk is starting its Run Before Queue jobs on the head commit. If the line says Run Before Queue failed to start, force the jobs and rerun, or push. See Failed to start.

Forks

A pull request from a fork has no access to your repository’s secrets, so the filter job has no token and every job runs.
No. Dynamic CI runs every job on them.