switch internal tools over to `go tool`
Open
internal
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 143
- Avg merge
- 4h 50m
- Merged PRs (30d)
- 1
Description
https://www.jvt.me/posts/2025/01/27/go-tools-124/ has a good description of how and why. this probably means gqlgen (used for tests), golangci-lint, maybe more
Contributor guide
Research direction
Start with the linked Go tools article, then inspect how gqlgen is used for tests and how golangci-lint is invoked. Identify any additional internal tools in the repository and migrate the relevant tool setup to Go's tool mechanism; done means the listed tools work through the new setup and tests and linting still run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100