wolfi-dev / wolfi-dev/wolfictl
`wolfictl lint` doesn't print out actual error
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 73
- Forks
- 86
- Avg merge
- 7d 7h
- Merged PRs (30d)
- 15
Description
Description
It just prints the linting failed error, but we can't see the actual error unless we pass the --log-level debug flag:
wolfictl lint .
2025/03/17 14:14:35 ERRO linting failed
wolfictl lint --log-level error
2025/03/17 14:14:35 ERRO linting failed
Action doesn't have this flag: https://github.com/wolfi-dev/actions/blob/117317a80d8d1e32227a90838672b34f04fa65b3/wolfictl-lint/action.yaml#L27
Contributor guide
No contributing guide indexed for this repository
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 reproducing the failure with wolfictl lint . at the default log level, then inspect the wolfictl lint command and wolfictl-lint/action.yaml at the referenced line. Done means the command exposes the actual lint error without requiring --log-level debug, including when invoked by the action.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100