Skip to content

ci: a pull request that changes only docs skips CI - #449

Merged
turbolytics merged 1 commit into
mainfrom
ci/pr-paths-filter
Oct 9, 2026
Merged

turbolytics merged 1 commit into
mainfrom
ci/pr-paths-filter

Conversation

@turbolytics

Copy link
Copy Markdown
Owner

What this changes

A pull request that changes only docs or Markdown no longer runs CI. The
pull_request trigger carries a paths filter that leaves out docs/** and
every .md file. docs/coverage/** stays in, because the Coverage job
regenerates the page there.

CI on a push now runs for main only. Before, it ran on every branch. Leaving
that in place would make the filter a no-op, since a docs-only branch would
still run CI through its push. It also ran every pull request twice.

What to check

  • A branch without a pull request no longer runs CI. Open a pull request,
    or a draft one, to get a run.
  • A README.md-only change skips CI. One test asserts the README's metrics
    table against the running exporter. A README edit that breaks that table
    shows on the push to main, not on the pull request.
  • Nothing can block a merge. The only required check is CLA, which runs
    on pull_request_target and is unaffected.

Verification

The workflow YAML parses, and its on block reads back as written. This pull
request changes a workflow, so its own CI run proves the trigger fires.

A pull request that touched only Markdown or docs/ ran every CI job.
That spent runner time on changes that cannot break a build. The
pull_request trigger now carries a paths filter that leaves those out.
docs/coverage stays in, because the Coverage job regenerates the page
under it.

CI on a push now runs for main only. Before, it ran for every branch,
so a docs-only pull request would have run CI through its push anyway,
and every other pull request ran CI twice.

If the filter is wrong, a pull request that needed CI merges without
it. The push to main still runs the full suite, so the break shows on
main instead of on the pull request. No check is required to merge, so
a skipped run cannot block a pull request.
@turbolytics
turbolytics merged commit a7f103b into main Oct 9, 2026
7 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 9, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant