Not able to commit changes when using GPG-autosigned commits
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
To be fair, it's entirely possible I'm just a noob or an idiot here. I have my Git config set up to automatically sign my commits using a GPG signature, which is configured with a passphrase. However, that means when I try to commit changes using the T3 Code interface, it simply returns an error, as there is no mechanism to accept my GPG passphrase.
This leaves me with one of two options:
- Update my Git config so automatic signing is turned off
- Manually commit changes using the terminal
As of right now, I've chosen the latter.
Edit: Just realized I can configure the Git config locally. Still not ideal, but a better temporary solution.
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 in the T3 Code interface's commit flow and reproduce the issue with Git automatic signing enabled and a passphrase-protected GPG key. Trace how the flow handles the commit authentication step; done means users can commit through the interface without disabling signing or switching to the terminal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100