Re-work all error messages
Open
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 603
- Forks
- 548
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 1
Description
I'll re-work all error messages in a separate PR once I am happy with nft-utils
Originally posted by @maxulysse in https://github.com/nf-core/sarek/pull/1975#discussion_r2337093273
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
Review the issue context and the referenced nft-utils work before defining the scope of the separate PR. Done means re-working all error messages after nft-utils is considered satisfactory, but the issue does not name files, tests, or specific messages.
Written by the indexing model from the issue text.
Assessment
- Domain
- bioinformatics
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100