Skip to content

[v3-2-test] CI: Run CodeQL only on languages changed in a pull request (#67972) - #68024

Merged
shahar1 merged 1 commit into
apache:v3-2-testfrom
shahar1:backport-67972
Jun 4, 2026
Merged

[v3-2-test] CI: Run CodeQL only on languages changed in a pull request (#67972)#68024
shahar1 merged 1 commit into
apache:v3-2-testfrom
shahar1:backport-67972

Conversation

@shahar1

Copy link
Copy Markdown
Contributor

Backport of #67972 to v3-2-test.

This change makes CodeQL analysis more efficient by only running scans on languages whose files actually changed in a PR, while maintaining full coverage on pushes to main and scheduled runs.


Generated-by: Claude Code (Haiku 4.5) following the guidelines

)
PR-triggered CodeQL is by far the most frequent workflow in the repo
(~1,300+ runs/week), and every run fans out one job per language
(python, javascript, actions, go, java) regardless of what changed.
The java job in particular runs a full Gradle build on every PR even
though java-sdk files change in well under 1% of PRs.
Gate the language matrix on the files actually changed in the PR: a
docs-only PR now runs nothing, and the common python-only PR runs a
single job instead of five. push-to-main and scheduled runs still scan
every language, so coverage of the main branch is unchanged.
(cherry picked from commit c91dc3b)
@shahar1shahar1 changed the title CI: Run CodeQL only on languages changed in a pull request[backport] CI: Run CodeQL only on languages changed in a pull request (#67972)Jun 4, 2026
@shahar1shahar1 changed the title [backport] CI: Run CodeQL only on languages changed in a pull request (#67972)[v3-2-test] CI: Run CodeQL only on languages changed in a pull request (#67972)Jun 4, 2026
@shahar1
shahar1 merged commit 24edb9f into apache:v3-2-testJun 4, 2026
109 checks passed
@shahar1
shahar1 deleted the backport-67972 branch June 4, 2026 21:18
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@shahar1@bugraoz93@amoghrajesh