Repository navigation
ci: run workflows on PRs into release/v* branches - #48
Merged
Merged
Conversation
Project policy routes every PR through a release/v* branch before main, so PRs into release/v0.2.0 otherwise get no tests.
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.
Every PR in this project now targets
release/v0.2.0, andember.ymlandserver.ymlonly ran for PRs intomain, so #44 and #47 had no tests. This adds'release/v*'to bothpull_requesttriggers.Merge this first:
pull_requestruns use the workflow files from the merge of head into base, so once it is inrelease/v0.2.0the other PRs pick up CI on their next push (or close and reopen).CodeQL uses GitHub's default setup, which scans PRs into the default branch only; it will run on the release PR into
main.