cb-technologies / cb-technologies/existe-id
Integrate a Linter Tool to insure the quality of our code
Open
- Dominant language
- Go
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
We can use revive for this or another go linter here
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the repository's Go setup and identify where development or CI checks are configured; no files or tests are named in the issue. Compare revive with other Go linters, then define the integration point and verify that the selected linter runs successfully against the repository's code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100