Git Store Credential - Shell/Bash

Introduction

As a programmer, it is common to work with Git for version control. Git provides a way to store credentials to avoid entering usernames and passwords every time you interact with a remote repository. This can be convenient and save time, especially when working with multiple repositories or collaborating with a team.

This guide will explain how to store Git credentials using the Shell/Bash command line interface. We will cover both the global and local configurations, and how to manage and remove stored credentials.

Storing Git Credentials

To store Git credentials, you can use the following Shell/Bash command:

$ git config --global credential.helper store

This command sets the credential.helper configuration to use the "store" helper, which will store credentials in an unencrypted plain text file on your local machine. Note that this method may not be suitable for sensitive credentials.

You can also set the configuration only for a specific Git repository by omitting the --global option and running the command in the repository's directory.

After running this command, the credentials you enter during authentication (username and password or personal access token) will be cached and automatically used in future Git operations without prompting.

Managing Stored Credentials

Viewing Stored Credentials

To view the stored credentials, you can open the file where the credentials are stored. By default, Git stores credentials in the .git-credentials file in your home directory. You can open and view the file with a text editor:

$ nano ~/.git-credentials

Removing Stored Credentials

To remove stored credentials, you can simply delete the .git-credentials file or edit it to remove the specific entry. Alternatively, you can use the following Git command:

$ git credential-store --clear

This command clears all stored credentials from the store.

Conclusion

Storing Git credentials can be helpful for avoiding repetitive authentication during Git operations. By utilizing the Shell/Bash command line interface, you can configure Git to store credentials either globally or locally per repository. Be cautious when storing sensitive credentials and consider more secure methods like encrypted credential helpers.