Add advanced CodeQL setup to replace broken default setup - #37
Merged
Conversation
The enterprise-enforced security config disables code scanning default (automatic) setup, which has left this repo's default CodeQL analysis stuck erroring since 2025-05-14. Adding an explicit workflow switches to advanced setup, which is unaffected by that policy.
This was referenced Jul 24, 2026
Merged
Merged
Merged
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
1 participant
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
Gusto Default Advanced Security, enforced) disables code scanning default (automatic) setup org/enterprise-wide, overriding this org's own "enabled" setting.rubyandactionslanguage configs since 2025-05-14 (the date the enterprise policy took effect), which is what shows up as "Errors detected in 2 configurations" on the CodeQL status page..github/workflows/codeql.yml, an explicit advanced setup workflow covering the same two languages. Pushing an advanced CodeQL workflow causes GitHub to automatically supersede the broken default-setup state, since advanced setup isn't subject to the same enterprise policy.Test plan
CodeQLworkflow runs successfully onmainfor both therubyandactionsmatrix jobs