Limit CI triggers to avoid duplicate runs on PRs #207
Conversation
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.
Same refs spin up CI twice for both being the branch head, and the PR head:
which is not really necessary. (And can even introduce confusion, as branch pushes run in the context of the repo branch and the actual sha, whereas PR triggers run unprivileged and on "merge head", i.e. the future ref that would happen after merging — showing better forward compatibility before any surprises land on main…)
This simplifies that by limiting the runs to just the default branch (and tags), and PR pushes separately.
(Also bumps all actions versions to current major releases).
Test runs of the template repository on push and tag:
(Also closes #204 and resolves #203 as superseded.)