prometheus / prometheus/common
Block any further extractions to common/config
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 295
- Forks
- 367
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 18
Description
I want this issue to serve as a canonical blocker to extract any further structs into common/config.
I consider it largely harmful and do not want this rabbit hole to grow until we've given our overall strategy on shared functionality a revisit.
That's a longer discussion we shouldn't have here, so I'll elaborate on the full details elsewhere later.
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
The issue names common/config as the area to inspect but provides no file, test, entry point, or concrete implementation change. Read the existing common/config package and determine the broader shared-functionality strategy first; the issue does not define a technical done condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100