Skip to content

ci: skip PR test suites for docs-only changes#2326

Closed
aryanku-dev wants to merge 1 commit into
masterfrom
ci/skip-ci-for-docs-only-prs
Closed

ci: skip PR test suites for docs-only changes#2326
aryanku-dev wants to merge 1 commit into
masterfrom
ci/skip-ci-for-docs-only-prs

Conversation

@aryanku-dev

@aryanku-dev aryanku-dev commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Closed — out of scope. Decision is to apply the docs-only CI skip to the Buildkite repos only, not the GitHub Actions CLI/SDK repos. Tracking: PER-9796.


What (original)

Skip the full CI suite on pull requests that change only documentation, so a README/.md/.txt/docs/ PR doesn't spend ~an hour of Linux + Windows + macOS runners.

Approach: a reusable detector (.github/workflows/_changes.yml) plus job-level gates on every PR-triggered workflow. Superseded by the Buildkite-only decision; left here for reference.

Add a shared reusable detector (.github/workflows/_changes.yml) that resolves a
single `code` output: 'false' when a pull request changes only documentation
(*.md, *.txt, README*, LICENSE, docs/**) and 'true' otherwise. The PR-triggered
workflows (lint, typecheck, test, windows, executable-check, semgrep) gate their
jobs on it, so docs-only PRs skip the suites.

A skipped required job is treated as passing by branch protection, so docs-only
PRs still satisfy required checks and can merge with no tests run. The gate is
fail-safe: only a clean docs-only pull_request yields 'false'; every other event
(push to master, workflow_dispatch, schedule), an empty/failed diff, or any
non-docs path (incl. workflows, lockfiles, Dockerfiles) runs the full suite. The
existing release-PR skip is preserved.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@aryanku-dev aryanku-dev requested a review from a team as a code owner June 29, 2026 05:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant