Enable CI tests for other branches than dev
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe
I'd like to do some tests on another branch dsl2 on which we're working in Sarek.
Can't and won't merge it in its current state in dev, but linting is failing all the time if I enable CI in this specific branch.
Describe the solution you'd like
I'd like to have CI enabled on other branches without nf-core lint failing
Describe alternatives you've considered
Having nf-core lint fail and keep my CI tests on, which is what I'm currently doing
Additional context
Same issue for CI on master as discussed on slack
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 tracing how CI configuration and nf-core lint are applied to branches such as dev, dsl2, and master. Confirm the intended branch-selection behavior, then use the existing CI and lint checks to verify that other branches can run tests without lint blocking them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- 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