ci: run on pull requests onto any base branch - #84
Merged
Conversation
The pull_request trigger was filtered to main and release/**, so a PR stacked onto another feature branch got no lint, build, test or eval run and merged unchecked. Drop the filter; the push trigger keeps its filter, so branch pushes do not double up.
lcottercertinia
approved these changes
Aug 2, 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.
The
pull_requesttrigger was filtered tomainandrelease/**, so a PR stacked onto another feature branch got no lint, build, test or eval run — #81 and #83 both show zero checks today, and would merge unchecked.Dropping the filter makes every pull request run CI, whatever its base. The
pushtrigger keeps itsmain/release/**filter, so pushing a feature branch still does not start a second, duplicate run.One line, no job changed.