Setup and Config
Getting and Creating Projects
Basic Snapshotting
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
Patching
Debugging
External Systems
Server Admin
Guides
- gitattributes
- Command-line interface conventions
- Everyday Git
- Frequently Asked Questions (FAQ)
- Glossary
- Hooks
- gitignore
- gitmodules
- Revisions
- Submodules
- Tutorial
- Workflows
- All guides...
Administration
Plumbing Commands
- 2.43.1 → 2.52.0 no changes
- 2.43.0 2023年11月20日
- 2.27.1 → 2.42.4 no changes
- 2.27.0 2020年06月01日
- 2.18.1 → 2.26.3 no changes
- 2.18.0 2018年06月21日
- 2.10.5 → 2.17.6 no changes
- 2.9.5 2017年07月30日
- 2.5.6 → 2.8.6 no changes
- 2.4.12 2017年05月05日
- 2.2.3 → 2.3.10 no changes
- 2.1.4 2014年12月17日
- 2.0.5 2014年12月17日
NAME
git-credential-store - Helper to store credentials on disk
SYNOPSIS
git config credential.helper 'store [options]'
DESCRIPTION
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
gitcredentials[7] or EXAMPLES below.
OPTIONS
EXAMPLES
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]
STORAGE FORMAT
The .git-credentials file is stored in plaintext. Each credential is
stored on its own line as a URL like:
https://user:pass@example.com
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[7] for more information.
GIT
Part of the git[1] suite