Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.10.0 → 2.12.0 no changes
- 2.9.3 08/12/16
- 2.5.2 → 2.9.2 no changes
- 2.5.1 08/28/15
- 2.5.0 07/27/15
- 2.4.10 no changes
- 2.4.9 09/04/15
- 2.4.4 → 2.4.8 no changes
- 2.4.3 06/05/15
- 2.4.1 → 2.4.2 no changes
- 2.4.0 04/30/15
- 2.3.9 09/04/15
- 2.2.0 → 2.3.8 no changes
- 2.1.4 12/17/14
- 18.104.22.168 → 2.1.3 no changes
- 1.8.2 03/13/13
|Using this helper will store your passwords unencrypted on disk, protected only by filesystem permissions. If this is not an acceptable security tradeoff, try git-credential-cache, or find a helper that integrates with secure storage provided by your operating system.|
This command stores credentials indefinitely on disk for use by future Git programs.
You probably don’t want to invoke this command directly; it is meant to
be used as a credential helper by other parts of git. See
<path>to lookup and store credentials. The file will have its filesystem permissions set to prevent other users on the system from reading it, but will not be encrypted or otherwise protected. If not specified, credentials will be searched for from
$XDG_CONFIG_HOME/git/credentials, and credentials will be written to
~/.git-credentialsif it exists, or
$XDG_CONFIG_HOME/git/credentialsif it exists and the former does not. See also FILES.
If not set explicitly with
--file, there are two files where
git-credential-store will search for credentials in order of precedence:
User-specific credentials file.
Second user-specific credentials file. If $XDG_CONFIG_HOME is not set or empty,
$HOME/.config/git/credentialswill be used. Any credentials stored in this file will not be used if
~/.git-credentialshas a matching credential as well. It is a good idea not to create this file if you sometimes use older versions of Git that do not support it.
For credential lookups, the files are read in the order given above, with the first matching credential found taking precedence over credentials found in files further down the list.
Credential storage will by default write to the first existing file in the
list. If none of these files exist,
~/.git-credentials will be created and
When erasing credentials, matching credentials will be erased from all files.
The point of this helper is to reduce the number of times you must type your username or password. For example:
$ git config credential.helper store $ git push http://example.com/repo.git Username: <type your username> Password: <type your password> [several days later] $ git push http://example.com/repo.git [your credentials are used automatically]
.git-credentials file is stored in plaintext. Each credential is
stored on its own line as a URL like:
When Git needs authentication for a particular URL context, credential-store will consider that context a pattern to match against each entry in the credentials file. If the protocol, hostname, and username (if we already have one) match, then the password is returned to Git. See the discussion of configuration in gitcredentials for more information.
Part of the git suite