git-ecosystem / git-ecosystem/git-credential-manager
Add option/setting to suppress `erase` operation
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
Feature description
Static credentials (tokens) in automated contexts are normally valid until changed explicitly.
Transient failures should not lead to erase, especially as restore requires manual interaction.
Implementing this in a central place would be preferable to modifying each provider.
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
Trace the central credential-handling path where the erase operation is triggered, rather than starting with an individual provider. Identify how settings are defined and consumed, then verify that an opt-in setting prevents erase during transient failures while preserving the existing behavior by default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100