included_configs: false is only recognised as a test name in --release mode
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
Description of the bug
I have the following in my .nf-core.yml:
lint:
included_configs: false
When I run nf-core pipelines lint I get:
WARNING Found unrecognised test name 'included_configs' in pipeline lint config
But I don't get this warning with nf-core pipelines lint --release.
I would expect that this should be a recognised test name in both cases, even if the test is not applied in both cases?
Command used and terminal output
System information
No response
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 with the nf-core pipelines lint entry point and compare its normal and --release handling of .nf-core.yml test names. Reproduce the warning using included_configs: false in both modes. Done means included_configs is recognised consistently, with the expected test application behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100