-
Couldn't load subscription status.
- Fork 215
Remove the on_pull_request_target trigger from the download test. #3399
New issue
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
Remove the on_pull_request_target trigger from the download test. #3399
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
nf_core/pipeline-template/.github/workflows/download_pipeline.yml
Outdated
Show resolved
Hide resolved
b051b11 to
911b139
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
|
I am looking at the failing test now 👀 |
f933e58 to
72150cf
Compare
…flow logfile for debugging.
4d09d91 to
c81b818
Compare
I hope you fixed it, but I somehow can't launch a workflow run with the GH Action version from my branch in this repo. This works, because it is my fork: gh workflow run -R "MatthiasZepper/tools" --ref "download_action_trigger_refactor" "pytest.yml"but gh workflow run -R "nf-core/tools" --ref "refs/pull/3399/head" "pytest.yml"doesn't. Unfortunately, I have no clue what the correct ref would be. |
|
Hi @MatthiasZepper, I just pushed the fix. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files☔ View full report in Codecov by Sentry. |
I was confused about the failing test, because I recalled that you had before already modified the CI to adapt it to that change, and thus attributed that failure to an old version of the CI. To my best knowledge, it will always run the CI from |
Admittedly, I had used GitHub Copilot to pick the triggers for the Download test workflow. However, it turns out that running on
pull_request_targetis useless, since the download test will only be run on the release PRs fromdevtomain.and a released pipeline should have passed that test before.Additionally, I am removing the
editedweb hook, since editing the text of the PR description is not really a useful trigger for testing the download.PR checklist
CHANGELOG.mdis updateddocsis updated