ci: run checks on pull requests targeting any branch - #73
Merged
Conversation
Stacked pull requests target the branch below them rather than main. With the base-branch filter in place their checks never ran, so every layer above the bottom one reported no status at all.
Same reasoning as the CI workflow: a stacked pull request targets the branch below it, so the base-branch filter kept code scanning from ever reporting on 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
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.
Stacked pull requests target the branch below them rather than
main. With the base-branch filter on thepull_requesttrigger, their checks never ran and every layer above the bottom one reported no status at all.Dropping the filter keeps the same checks on every pull request, whatever its base.