git-ecosystem / git-ecosystem/git-credential-manager
gpg: Decryption failed: We don't have the secret key
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
Version
2.3.2
Operating system
Linux
OS version or distribution
Ubuntu 22.04.3 LTS
Git hosting provider(s)
GitHub
Other hosting provider
No response
(Azure DevOps only) What format is your remote URL?
None
Can you access the remote repository directly in the browser?
Yes, I can access the repository
Expected behavior
I don't know why I am getting this error if git connects to the repository and everything is successful
Actual behavior
I am getting this error but git connects to the repository and everything is successful
Logs
No response
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 source file, entry point, or failing test is identified. Start by reproducing the GPG decryption error with Git Credential Manager 2.3.2 on Ubuntu 22.04.3 while accessing GitHub, then trace whether the failure is in credential retrieval or Git authentication. Done means the cause and a verified resolution are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100