Remove nf-test latest for PRs and run nf-test latest on PR merge
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Instead of passing the latest nf-tests and everyone ignoring it, we want to run on the minimum Nextflow version in the template.
Then, when the PR is merged, we'll run the latest on CI to make sure it works.
Then we'll have a follow-up issue to open an automated issue that failed on the latest.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the CI entry points that invoke nf-test for pull requests and merges, then check how the template's minimum Nextflow version is selected. Done means PRs run nf-test at that minimum, merged PRs run the latest, and the follow-up automation remains separate.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100