Optimize CodeQL workflow - #5
Merged
Merged
Conversation
thrr87
marked this pull request as ready for review
July 27, 2026 07:42
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
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
Why
CodeQL Default Setup runs a full Swift autobuild for every pull request, including documentation-only changes. Recent Swift scans in this repository took about 14–22 minutes, while the normal test job finished in under a minute.
After the cutover, README, documentation, image, and license-only changes will not start CodeQL. Code and workflow changes will still be scanned, and the weekly scan remains in place.
The repository is public, so standard GitHub-hosted runners are currently free. This change reduces wasted runner time and pull request latency rather than fixing a current bill.
Checks
.github/workflows/codeql.ymlas YAMLgit diff --checkswift build --arch arm64Analyze (actions)in 33 secondsAnalyze (swift)in 12 minutes 56 seconds