nf-core / nf-core/seqinspector
Prefix all warns/errors with seqinspector
Open
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 28
- Forks
- 44
- Avg merge
- 11d 8h
- Merged PRs (30d)
- 2
Description
Prefix all warns/errors with [nf-core/seqinspector] to make it clear where the warning/error are the coming from
Originally posted by @jfy133 in https://github.com/nf-core/seqinspector/pull/209#discussion_r2965544999
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
Search the repository for all warning and error emission points, since the issue does not name specific files or tests. Update each message to use the requested [nf-core/seqinspector] prefix, then run the relevant pipeline checks to confirm every warning and error is consistently prefixed.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100