Using Separate Credentials in TortoiseGit: A Step-by-Step Guide to Protecting Your Repos

Discover how to configure TortoiseGit for using separate credentials for your work and private repositories using SSH keys and token-based authentication.
---
This video is based on the question https://stackoverflow.com/q/73970992/ asked by the user 'jackhab' ( https://stackoverflow.com/u/48461/ ) and on the answer https://stackoverflow.com/a/74110302/ provided by the user 'jackhab' ( https://stackoverflow.com/u/48461/ ) 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: Using separate credentials in TortoiseGit

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

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Using Separate Credentials in TortoiseGit: A Step-by-Step Guide to Protecting Your Repos

In today's fast-paced world of software development, many individuals manage multiple repositories, often for both work and personal projects. With platforms like Bitbucket and GitHub transitioning to token-based authentication, it’s crucial to understand how to maintain security and manage access effectively. If you’ve ever wondered how to keep your private repositories password-protected while seamlessly pushing to work repos without re-entering credentials, you’re in the right place. In this guide, we’ll walk you through the process of using separate credentials in TortoiseGit for your work and private repositories.

The Challenge of Managing Multiple Repositories

If you're like many developers, you might struggle with the following situation:

You have both work and private repositories on your Windows PC.

Both types of repositories are hosted either on Bitbucket or GitHub.

When you push to private repositories, the commits are incorrectly attributed to your work credentials.

This overlap can lead to confusion, especially if you want to protect your private repos while maintaining ease of use for your work repositories.

Solution Overview

The good news is that it is possible to configure TortoiseGit to push with the correct credentials for both repositories. This involves setting up SSH keys, which allow you to authenticate securely. Here’s how to do it:

Step 1: Generate Your SSH Key

First, you’ll want to create an SSH key for your private repositories. Here’s how:

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

This command generates a new SSH key and assigns an optional passphrase for additional security.

Make sure to replace USERNAME-mail.com with your actual email address.

Step 2: Add Your SSH Key to GitHub

Next, you’ll need to add your newly created SSH key to your GitHub account. Follow these steps:

Navigate to your GitHub account.

Go to Settings.

Select SSH and GPG keys.

Click on New SSH key and paste the contents of your id_ed25519.pub file.

Step 3: Test Your SSH Key

To ensure that your SSH key is working, execute the following command in your terminal:

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

If the configuration is correct, you’ll receive a success message indicating that you have successfully authenticated.

Step 4: Clone Your Repository via SSH

Now it’s time to clone your private repository using SSH. Here is the command you should use:

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

Replace USERNAME/REPO.git with the appropriate user name and repository name.

Step 5: Configure Repo Settings

For optimal function, add your SSH key to the local repository configuration by running:

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

Step 6: Optional - Set Local Repository Author

To ensure your commits are attributed correctly, you might want to set the local repo author information using these commands:

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

Step 7: Verify GitHub Access

Finally, confirm that everything is functioning as expected by executing a command to pull updates:

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

If there are no errors, your configuration is complete, and you are now set to push your commits to both work and private repositories without credential issues.

Conclusion

By following these steps, you can successfully manage multiple repositories with different credentials in TortoiseGit. This method not only keeps your private repositories protected but also allows you to push to your work repositories effortlessly. Embrace this configuration for a more organized and secure development environment.

Remember, securit

Видео Using Separate Credentials in TortoiseGit: A Step-by-Step Guide to Protecting Your Repos канала vlogize