git-ecosystem / git-ecosystem/git-credential-manager
Add optional feature of using same "config.email" and "config.name" as provider's account
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
Feature description
It's gets dubious when using multiple providers and accounts to manage configs in local repos, credential manager is good place to automatically decide config.email and config.name. Benefits are obvious, consistent commit history for same user, provider would recognize user by his email and name.
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
No file, test, or entry point is named in the issue. Start by clarifying how provider accounts should supply config.email and config.name across multiple providers, then trace the credential-manager flow that handles provider identity. Done means the behavior is optional, consistent for supported providers, and verified for multiple local repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- authentication, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100