Ability to specify origin for in-memory `Config` and overrides
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.2k
- Forks
- 265
- Avg merge
- 2h 42m
- Merged PRs (30d)
- 4
Description
When #97 gets implemented, it will probably also make sense to be able to set the origin when you create an in-memory Config object and when you set overrides.
The use case I have is to be able to implement something like git config --show-origin, where the application can set e.g. the origin to e.g. "GIT_EDITOR" or "environment" when it sets the value of core.editor based on the $GIT_EDITOR environment variable (although it seems git doesn't actually do it that way internally -- GIT_EDITOR=foo git config --show-origin core.editor doesn't show "foo").
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
Start by reviewing the design and implementation associated with #97, then trace how in-memory Config values and overrides are represented. Define how callers can provide an origin such as "GIT_EDITOR" or "environment", and verify that the origin remains available when configuration values are inspected or displayed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100