ci: Explicit types of pull requests and paths to run CI tests #933
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
ns-rse
force-pushed
the
ns-rse/922-ci-tests-all-pr
branch
from
8ba6ba2
to
3d71600
Compare
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.
Further to #925 it seems that not all pull requests are triggering the
tests.yamlworkflow.Not clear why #932 didn't trigger the
tests.yamlworkflow so this PR makes explicit thetypeof activity onpull_requestthat should trigger the event as well as explicitly stating the types of files that should trigger the tests via thepathsoption (as changes to e.g.*.md(Markdown) files are never going to affect the outcome of tests.