Repository navigation
ci: skip the scheduled CodeQL run while default setup is on - #2
Merged
Merged
Conversation
GitHub's default code scanning setup now scans this repository every week and refuses results uploaded by an advanced workflow. The workflow keeps its manual trigger for when default setup is switched off. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
GitHub's default code scanning setup is now on for this repository and scans Rust, TypeScript and the workflows every week. While it is on, GitHub refuses results uploaded by an advanced workflow, so the weekly run of
codeql.ymlwould fail. Its job now runs only when started by hand (for when default setup is switched off); the scheduled run is skipped.🤖 Generated with Claude Code