Скачать или смотреть How to Fix the Source Control Extension in VSCode for WSL with SSH Keys

Resolve issues with Git's `Source Control` extension in Visual Studio Code while using WSL and SSH keys, especially when a passphrase is involved.
---
This video is based on the question https://stackoverflow.com/q/69584056/ asked by the user 'jimbasso' ( https://stackoverflow.com/u/17158502/ ) and on the answer https://stackoverflow.com/a/69826320/ provided by the user 'jimbasso' ( https://stackoverflow.com/u/17158502/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: git extension in vscode in WSL window via SSH not working

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Fixing the Source Control Extension in VSCode for WSL Using SSH Keys

If you're using Visual Studio Code (VSCode) in Windows Subsystem for Linux (WSL) and having difficulties with the Source Control extension when it comes to git operations, you're not alone. Many developers have reported challenges when performing actions like cloning repositories through the GUI while using SSH keys with passphrases.

In this guide, we will delve into the common problems associated with using the Source Control extension in VSCode alongside SSH keys in WSL, and we'll provide you with a straightforward solution to get your git operations back on track.

The Problem

When you attempt to use the Source Control extension in VSCode for git actions (like cloning a repository) while in WSL, you may encounter several issues:

Cloning appears to start but doesn't complete: You might see the command executing in the output window, but nothing actually happens, and the tooltip indicating "Cloning git repository" hangs indefinitely.

SSH Passphrase not requested: Unlike when you're typing commands directly in the VSCode terminal, the extension may not prompt you for your SSH passphrase, leading to confusion and incomplete operations.

Specific Issues Noted:

The cloning process creates the repository folder and the .git subfolder but doesn’t copy any files.

Operations succeed when using the terminal directly, as long as you're willing to enter your passphrase.

The problem persists specifically when a passphrase is set for the SSH key, particularly if the key has its default name id_rsa.

The Solution

The good news is that there’s a simple solution that can resolve these issues and allow you to use your passphrase-protected SSH keys seamlessly with the Source Control extension in VSCode. Follow these steps:

Step 1: Configure Your .bashrc

Open Your .bashrc File

You can open this file in your preferred editor, or simply use the command:

[[See Video to Reveal this Text or Code Snippet]]

Add Keychain Configuration

Insert the following line at the end of your .bashrc:

[[See Video to Reveal this Text or Code Snippet]]

This line ensures that keychain manages your SSH keys correctly and asks for your passphrase only once per terminal session.

Save and Exit

If you're using nano, save your changes by pressing CTRL + X, then Y, and finally Enter.

Step 2: Restart Your WSL Terminal

To apply your changes:

Close your current WSL terminal session and open a new one. This will reload your .bashrc settings.

Step 3: Test in VSCode

Open your project in VSCode and try using the Source Control extension again. You should now be able to perform git operations seamlessly, even with passphrase-protected SSH keys.

Conclusion

By configuring your .bashrc to use keychain, you can effectively manage your SSH keys and eliminate the frustrating issues with the Source Control extension in VSCode while working in WSL. Now, you can focus on your code rather than technical hiccups with your git operations!

Feel free to leave a comment below if you encounter any issues or have questions about other development-related topics!