Trunk Dynamic CI and merge queues

Dynamic CI uses the branch to tell whether a run is for a pull request or a merge queue, and runs the two differently:

Pull requests are scored by the Dynamic CI engine, which skips jobs with nothing left to check.
Merge queues (Trunk Merge Queue’s trunk-merge/ branches) use your paths filters only. A job is skipped only when a paths filter excludes it. With no paths filter, every job runs.

If you want other conditions on when a job runs, add them to the job’s if:

if: >-
  !cancelled() &&
  needs.dynamic-ci-filter.outputs.unit-tests != 'false' &&
  github.ref != 'refs/heads/release'