ci: skip govulncheck, docker build, and CodeQL (go) on docs-only changes - #4459
Open
reinkrul wants to merge 1 commit into
Open
ci: skip govulncheck, docker build, and CodeQL (go) on docs-only changes#4459reinkrul wants to merge 1 commit into
reinkrul wants to merge 1 commit into
Conversation
Extends the docs-only skip pattern from #4455 (test, e2e-test) to the remaining workflows we control: govulncheck, the docker image build, and CodeQL's own Analyze (go) job. None of these are required status checks, but they still burn CI time/minutes on changes that can't affect Go code or the built image. Not touched: - govulncheck-cron-schedule.yaml: schedule/workflow_dispatch only, doesn't run on PRs, so the skip doesn't apply. - GitHub's repo-level "default setup" code scanning for Actions and JavaScript/TypeScript (shows up as Analyze (actions) and Analyze (javascript-typescript) in checks): not backed by a workflow file in this repo, so it can't be gated this way. Assisted by AI
reinkrul
requested review from
Dirklectisch,
JorisHeadease,
gerardsn,
stevenvegt and
woutslakhorst
as code owners
August 19, 2026 11:04
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
Comment on lines
44
to
53
Contributor
❌ 11 blocking issues (11 total)
|
Contributor
|
Coverage Impact This PR will not change total coverage. 🚦 See full report on Qlty Cloud »🛟 Help
|
4 tasks
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
2 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.
Summary
Extends the docs-only CI skip pattern from #4455 (
test,e2e-test) to the remaining workflows we control:govulncheck.yaml—govulncheck_jobbuild-images.yaml—dockercodeql-analysis.yml—analyze(Analyze (go))Same approach as #4455: a
changesjob usingdorny/paths-filterdetects whether anything outsidedocs/,*.md,*.rstchanged, and the real job is gated withneeds: changes+if: needs.changes.outputs.code == 'true'. A job skipped this way still reports as a passing check, so it's safe even if any of these were ever promoted to a required check later.None of these three are currently required status checks, so this is purely a CI time/cost optimization, not a merge-blocking change.
Not touched
govulncheck-cron-schedule.yaml: schedule/workflow_dispatchonly, doesn't run on PRs, so the skip doesn't apply.Analyze (actions)/Analyze (javascript-typescript)in checks): not backed by a workflow file in this repo, so it can't be gated this way — that's configured in repo Code Security settings.Test plan
.github/**, so all jobs should run (not skip) — confirm on CI