Use Namechk to see if your desired username or vanity url is still available at dozens of popular Social Networking and Social Bookmarking websites. Promote your brand consistently by registering a username that is still available on the majority of the most popular sites. Find the best username with Namechk. Securing your brand is important. Checkuser.org Social Username Checker We started our little tool Checkuser as Instagram Name Checker only, however ended up including more features like domain availability checker. With Checkuser you can find out if your desired username trademark or brand name is available on more than 70 Social Media sites, not only that also tool indicates. Free Origin account generator. Generate free Origin accounts now. Includes 20+ other free tools and resolvers. Free Origin account generator. Generate free Origin accounts now. Includes 20+ other free tools and resolvers.

To connect to a Git repository with authentication over HTTP(S), every time it needs to set a username and password.

You can configure Git to remember a username and password by storing them in a remote URL or by using Git credential helper.

In this article i am showing how to clone Git repository by setting a username and password on the command line, how to save a username and password in Git credentials storage and how to configure different usernames and passwords for different repositories on the same Git server.

Cool Tip: Show Git branch name in the command prompt! Read more →

Warning: Your Git credentials will be saved in a plaintext format in the files .git/config or ~/.git-credentials, depending on the method you choose.

Set Username and Password in Remote URL

To save credentials you can clone Git repository by setting a username and password on the command line:

The username and password will be stored in .git/config file as a part of the remote repository URL.

If you have already cloned a repository without setting username and password on the command line, you can always update the remote URL by running the following command:

Save Username and Password in Git Credentials Storage

Run the following command to enable credentials storage in your Git repository:

To enable credentials storage globally, run:

When credentials storage is enabled, the first time you pull or push from the remote Git repository, you will be asked for a username and password, and they will be saved in ~/.git-credentials file.

Origin Username Checker Free

During the next communications with the remote Git repository you won’t have to provide the username and password.

Each credential in ~/.git-credentials file is stored on its own line as a URL like:

Origin Username Checker

Config Username and Password for Different Repositories

Sometimes you may need to use different accounts on the same Git server, for example your company’s corporate account on github.com and your private one.

To be able to configure usernames and passwords for different Git repositories on the same Git server you can enable the useHttpPath option.

By default, Git does not consider the “path” component of an http URL to be worth matching via external helpers. This means that a credential stored for https://example.com/foo.git will also be used for https://example.com/bar.git. If you do want to distinguish these cases, set useHttpPath option to true (source)

Run the following commands to configure Git credentials storage and separate credentials for different repositories on github.com:

The usernames and passwords for different GitHub repositories will be stored in ~/.git-credentials file separately on their own lines:

Cool Tip: Create a new Git branch and checkout in one command! Read More →