Polluted log if GitHub Action is missing "on:"
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
If for whatever reason a GitHub workflow file is missing "on:" then a super long and not helpful error message is printed out:
Command used and terminal output
nf-core lint
System information
nf-core/tools version 2.8
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
Reproduce the issue with nf-core lint against a GitHub workflow file that lacks on: and inspect where the long error is emitted. Trace the lint error-handling entry point, then verify that the missing key produces a concise, helpful message instead of the polluted output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100