Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- All guides...
- 2.40.1 → 2.41.0 no changes
- 2.40.0 03/12/23
- 2.39.1 → 2.39.3 no changes
- 2.39.0 12/12/22
This command caches credentials in memory for use by future Git programs. The stored credentials never touch the disk, and are forgotten after a configurable timeout. The cache is accessible over a Unix domain socket, restricted to the current user by filesystem permissions.
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
- --timeout <seconds>
Number of seconds to cache credentials (default: 900).
- --socket <path>
<path>to contact a running cache daemon (or start a new cache daemon if one is not started). Defaults to
~/.git-credential-cache/exists in which case
~/.git-credential-cache/socketis used instead. If your home directory is on a network-mounted filesystem, you may need to change this to a local filesystem. You must specify an absolute path.
CONTROLLING THE DAEMON
If you would like the daemon to exit early, forgetting all cached
credentials before their timeout, you can issue an
git credential-cache exit
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 cache $ git push http://example.com/repo.git Username: <type your username> Password: <type your password> [work for 5 more minutes] $ git push http://example.com/repo.git [your credentials are used automatically]
You can provide options via the credential.helper configuration variable (this example drops the cache time to 5 minutes):
$ git config credential.helper 'cache --timeout=300'
Part of the git suite