Run CodeQL only on the template repository - #10
Merged
Conversation
Repos created from this template don't have code scanning enabled, so the CodeQL analyze/upload step fails and the branch appears to crash. Guard the analyze job to run only on the canonical template repo, which works across all triggers including schedule. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.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
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.
Problem
When a student uses this repo via Use this template, the created repo doesn't have code scanning enabled. The CodeQL
analyzejob's upload step then fails, making the branch appear to crash for every student instance.Fix
Guard the
analyzejob in.github/workflows/codeql-analysis.ymlso it runs only on the canonical template repository:Why match by repo name instead of
is_templateThe
scheduletrigger doesn't populategithub.event.repository, so anis_template-based check would silently disable the weekly scan on the template too. Matching the source repo name works uniformly acrosspush,pull_request,workflow_dispatch, andschedule.