microsoft / microsoft/vscode-remote-release
VSCode Remote should ask for GPG password using the standard VS Code passphrase input when git needs the GPG commit passphrase
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
VSCode Remote should ask for GPG password using the standard VS Code passphrase input when git needs the GPG commit passphrase.
I can't make sense out of what I'm supposed to setup to get it to work properly. I would have assumed that signing was natively implemented, but no one seems to give that as an option. When I remote into a VM to work on code, I sometimes have the GPG stored on the remote VM rather than on my local computer.
Apparently I'm the only person that does this, except for the GPG indicator plugin, but that was having problems for me.
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 reproducing a signed Git commit in a VS Code Remote session where the GPG key is on the remote VM, and observe how the passphrase request currently appears. No file or test is identified in the issue, so locate the Remote integration and standard VS Code passphrase input before defining the change. Done means Git signing prompts through the standard VS Code passphrase UI in this setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, vscode
- Domain
- devtools, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100