Add more path filters and manual triggers to GitHub Actions workflows #7280
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.
I noticed that in my previous PR to fix a minor formatting typo that a lot of CI was run (#7276). To reduce the required resources and also increase the speed of development, I added some more path-based filters to the GitHub Actions workflow triggers. Specifically:
rchk
if a file insrc/
is updatedinst/tests/
,R/
,src/
, ortests/
is updatedI also added the manual trigger
workflow_dispatch
. This is convenient when preparing a PR. As a developer, I can manually run a workflow on my feature branch in my feedstock (ie not the master branch), prior to opening the PR.I didn't add any path filters to
code-quality.yaml
orR-CMD-check.yaml
so that a baseline of CI is still run for every PR, but I could add them if requested.