Don't do GitHub CI "push" runs on non-default branches #185
Conversation
This file contains 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.
The "Test fetching tinuous' logs" workflow is currently failing because it ran so much that we exceeded some rate limit. This can be addressed by not running the workflow on pushes to non-default branches. Note that it will still run on pushes to PR branches, as that's a separate trigger; we're currently running all tests twice on PRs, with the only difference being that the PR triggers are run on the code as it would be after merging.
I also applied the same change to the normal test workflow for similar reasons.
Note that I included
[skip ci]in the commit message for this PR, so there will be no workflow runs, as I'm trying not to waste rate limits.EDIT: I have also configured the workflows so that, if a push is made to branch while an older workflow is still running on the branch, the older workflow is cancelled.