Repository navigation
docs: leave CodeQL out of the templates - #6
Merged
Merged
Conversation
Public repositories in the org now get CodeQL through default setup (the GitHub recommended security configuration), which rejects results from a separate CodeQL workflow. codeql.yml stays for repositories without it.
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.
Public repositories in the org get CodeQL through default setup since the "GitHub recommended" security configuration was attached to them. With default setup on, GitHub rejects results from a separate CodeQL workflow, so a
codeqljob in a template would failStatus checks passed.templates/workflows/status-checks-go.yml,status-checks-node.ymlandterraform.yml: nocodeqljob.codeql.ymlstays for repositories without default setup.Part of YIV-401.