Consolidate all the linting
- Dominant language
- No language data
- Stars
- 11
- Forks
- 25
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 3
Description
We have a style.yaml and linter here and other places (see below) there also exists other projects that have linters/actions to do similiar thing. One should go through these and come up with a good solution we can use across all repos.
https://github.com/knative/serving/blob/main/.golangci.yaml
https://github.com/golangci/golangci-lint-action
https://golangci-lint.run/usage/linters/
https://github.com/chainguard-dev/actions
https://github.com/dataheld/workflows/blob/main/.github/workflows/linter_reusable.yml
Contributor guide
Research direction
Start by locating the repository's style.yaml and linter configuration, then compare them with the linked Knative Serving, golangci-lint, Chainguard, and dataheld workflow examples. Done means a shared linting approach is selected and its scope across repositories is clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, yaml
- Domain
- ci-cd, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100