Block any further extractions to common/config

Open
#97 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
backend

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.

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.

Dominant language
Go
Stars
297
Forks
380
Avg merge
3d 18h
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from prometheus/common

All issues in prometheus/common

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.