#Visual studio code git email install

The complete setup worked on a fresh install of the current stable version of Windows 10 (2004 Build 19041.450). Thankfully we can use GnuPG to sign our commits which in turn allows Github to verify that the changes were authored by us and not some imposter.Ī handy bonus of signing our commits is that GitHub will now also show a verified tag allowing everybody to see we're trustworthy. It won't grant access to any private repositories or elevate rights on GitHub. It may be worth noting that this only allows someone to change the author of commits. In theory, this would allow anybody to impersonate someone else when committing code by using the email address associated with the other person's GitHub account. Thankfully, I have now solved it! A brief intro about signed commitsĬommits in git will be attributed to whatever values you have set against the name and email fields in your gitconfig. I don't mind using a separate terminal to run my git commands, but it's just so convenient to do it within my editor. But I couldn't find a way to display a pinentry within Windows 10 when using either the Visual Studio Code git interface or the built-in terminal. The issue? The passphrase prompt would not show up.Ī pinentry to enter my passphrase for signed commits is displayed inside Windows Terminal if I set it up to display via TTY and do all of my git commands from within the terminal. The one (minor) gripe holding me back was the inability to use signed commits from within Visual Studio Code when code, git and the gpg agent are running inside of WSL2. I haven't completely moved away from MacOS but the experience is so enjoyable that I will likely switch to a Surface Book when it comes time to upgrade my MacBook Pro.

I have recently been spending more and more time doing web development on Windows 10 using WSL2 and Windows Terminal.