We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should only run pipeline tests/nf-test if actual 'code' files have changed.
If a PR only has markdown/docs changes, then we shouldn't waste compute time on testing the pipeline (as nothing has changed)
The text was updated successfully, but these errors were encountered:
One issue may be how to change 'merge requirements' of such PRs however
Sorry, something went wrong.
No branches or pull requests
Description of feature
We should only run pipeline tests/nf-test if actual 'code' files have changed.
If a PR only has markdown/docs changes, then we shouldn't waste compute time on testing the pipeline (as nothing has changed)
The text was updated successfully, but these errors were encountered: