ci: skip the heavy unit-tests suite for docs-only pull requests - #15699
Merged
Conversation
A pull request that only touches docs/ triggered the full unit-tests matrix (docker builds, REST framework, UI/integration, k8s, performance) on every push. Add paths-ignore: ['docs/**'] to the pull_request trigger so an exclusively-docs PR skips it. A PR that touches any code alongside docs still runs the full suite. This is scoped to the pull_request trigger only. The merge_group trigger stays unfiltered because GitHub ignores paths/paths-ignore for merge_group events, so a docs-only PR is still built and tested in full when it reaches the merge queue and the required `Unit Tests Complete` check is still produced there. The PR-level required check `ruff-linting` runs from its own workflow and is unaffected. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
blakeaowens
approved these changes
Aug 18, 2026
devGregA
approved these changes
Aug 18, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 18, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 18, 2026
Maffooch
added a commit
that referenced
this pull request
Aug 18, 2026
…5712) The paths-ignore filter added this morning (#15699) skipped the whole unit-tests workflow on docs-only pull requests, so the required `Unit Tests Complete` context was never created and sat as "Expected -- waiting for status to be reported" forever. A pull request must pass its required checks before it can be added to the merge queue, so docs-only PRs (#15710, #15711) became unqueueable for anyone without ruleset bypass. The change assumed the merge_group run would satisfy the requirement, but that run only happens after the PR enters the queue. Keep the CI savings by moving the skip from the trigger to the jobs: a `changes` job lists the PR's files and outputs docs_only, the heavy build/test chain skips when it is true, and the unit-tests-complete gate accepts skipped dependencies only in that case. The gate now reports success in seconds on docs-only PRs instead of never, and merge_group runs still execute the full two-platform matrix because docs_only is only computed on pull_request events. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[sc-14594]
Problem
A pull request that changes only
docs/still triggers the entireunit-testsmatrix — docker image builds, REST framework tests, the full UI/integration suite, k8s deployment, and performance tests — and re-runs it on every push. That is a large amount of runner time spent on changes that cannot affect any of those tests.Fix
Add
paths-ignore: ['docs/**']to thepull_requesttrigger ofunit-tests.yml. Becausepaths-ignoreonly skips a PR whose changes are entirely underdocs/, a PR that touches any code alongside docs still runs the full suite — this never under-tests real changes.Why this is safe (required checks)
pull_requesttrigger only. Themerge_grouptrigger is left unfiltered, and GitHub ignorespaths/paths-ignoreformerge_groupevents, so a docs-only PR is still built and tested in full when it enters the merge queue, and the requiredUnit Tests Completecheck is still produced there. No "skipped but required" check hangs the PR.ruff-lintingruns from its own workflow (ruff.yml), unaffected by this change.Net effect: docs-only PRs skip redundant per-push runs during review, and are still fully tested at merge time via the queue. No test coverage is lost.
🤖 Generated with Claude Code