Skip to main content
Path filters describe which changed files are relevant to a job. Set them per job on the Configuration tab in the Trunk web app. See Jobs to find and expand a job.

Syntax

Path filters use the same glob syntax as dorny/paths-filter: the job’s name followed by a list of patterns.
You can edit filters in the Visual editor or switch to YAML. To read or set them in bulk, use the paths filters API, which is in beta.

How filters affect a verdict

By default, path filters are another signal into the scoring engine rather than a hard rule. A change that matches a job’s filters makes the engine more likely to run it, and a change that touches none of them makes a skip more likely, but the engine still weighs the job’s history and the pull request’s state before deciding. In the merge queue, Dynamic CI skips a job only when its path filters say the change does not touch it. With no path filters, every job runs. See Merge queues. Jobs with path filters show a Path filters badge in the job list.