livepeer / livepeer/go-livepeer
Run golangci-lint on all packages
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 586
- Forks
- 226
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 19
Description
We currently only run golangci-lint on certain packages in CI. We should run golangci-lint locally, fix all the warnings/errors and then start running golangci-lint on all packages in CI. The one thing to consider here is which linters should be enabled by default (or just use the default linters used by golangci-lint).
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 .github/workflows/linux.yml around line 67 to see which packages golangci-lint currently checks. Run golangci-lint locally across all packages, review the resulting warnings and errors, and decide which linters should be enabled. Done means the reported issues are fixed and CI checks all packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100