Lint parts of CI template
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Description of feature
Just a foot gun I shoot myself with often. If you turn off the CI file check, then you miss version bumps in the file (or at least I do 🙃).
It might already be checking for things but we could make sure the version matches the current Nextflow version we want to support.
https://github.com/nf-core/demultiplex/pull/155#pullrequestreview-1776843147
Ideally though I'd like to move most of the logic to a central actions repo, and with nf-test most of the creative stuff people have to do should just go away.
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 reviewing the CI file-check behavior discussed in nf-core/demultiplex pull request 155 and the proposed centralization in nf-core/setup-nextflow issue 22. Define how the template should verify that its Nextflow version matches the supported version, then confirm the check catches version bumps without disabling other CI checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100