Remove testing of `latest-everything` from every single PR CI run
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Currently every PR on an nf-core pipeline repository will run the tests on both latest stable and edge release.
However because of nf-test sharding we don't actually report a failure of latest-everything to prevent blocking of merging on the PR conversation tab which is where most people look to see their test status (polling the maintainers team, people rarely check the 'Run nf-test' summary page in the 'checks' tab).,
I suggest we remove the latest-everything runs from every PR, maybe reserving only for release PRs from dev to master, to help reduce our environmental impact.
@mirpedrol also points out we have 'nightly builds' which should help us detect if upcoming Nextflow changes will cause problems.
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
The issue names no files or tests; start by locating the PR CI definitions that run latest stable and edge releases, then review how nightly builds and release PRs are handled. Done means ordinary PRs no longer run latest-everything while the intended release or nightly coverage remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100