Run CI and CodeQL on roller-6.1.x - #206
Merged
Merged
Conversation
The maintenance branch is maintained alongside master, so pushes and pull requests that target it need the same build, tests and code scanning.
mbien
approved these changes
Oct 4, 2026
This was referenced Oct 4, 2026
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
2 participants
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.
Both workflows on
roller-6.1.xtrigger only formaster, so PRs to the maintenance branch (#198, #199, #200, #201, #205) get no build, tests or CodeQL scan.This adds
roller-6.1.xto thepushandpull_requestbranch filters inmain.ymlandcodeql-analysis.yml.masterstays in the lists so the change can be cherry-picked to master without effect.After merge, re-run checks on open 6.1.x PRs (push a commit, or close and reopen).