Add gallagher branch to CodeQL workflow triggers - #2
Open
StephHope wants to merge 1 commit into
Open
Conversation
StephHope
marked this pull request as draft
July 30, 2026 21:50
StephHope
marked this pull request as ready for review
July 30, 2026 21:50
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.
Add
gallagherto CodeQL's trigger branchesadvanced-codeql.ymlcurrently only scansmain-enterprise(push and PR). Sincegallagheris now this repo's default and control branch, none of our own changes ever get scanned —main-enterpriseonly ever sees genuine upstream commits, never anything we add on top.This adds
gallagheralongsidemain-enterprise(not replacing it), so:main-enterprisekeeps scanning incoming upstream content as it lands — a useful automated check on top of the tracking branch's review, which is provenance-only ("is this really from upstream?"), not a content/security review.gallaghernow scans everything Gallagher-authored: in-tree fixes (e.g.teams.js), workflow/config changes like this one, and future upstream integration merges — none of whichmain-enterprise's trigger would ever catch.No functional change to what CodeQL analyzes, just where it runs. Also needed as a prerequisite for
gallagher's CodeQL checks to be selectable as required status checks later, since GitHub only offers checks it's actually seen run.