path: root/Documentation/git-credential.txt
diff options
authorMatthieu Moy <>2012-06-24 11:40:00 (GMT)
committerJunio C Hamano <>2012-06-25 18:56:24 (GMT)
commit2d6dc182b8fa171a6b283ce6e8e75a35e13ea67a (patch)
tree8f2e6170136cf7a4a63b8ef6083327e91c8c4fae /Documentation/git-credential.txt
parente30b2feb1b50c2d14d32dc3e6e41f7b20a677ff2 (diff)
git credential fill: output the whole 'struct credential'
Instead of outputing only the username and password, print all the attributes, even those that already appeared in the input. This is closer to what the C API does, and allows one to take the exact output of "git credential fill" as input to "git credential approve" or "git credential reject". Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'Documentation/git-credential.txt')
1 files changed, 12 insertions, 4 deletions
diff --git a/Documentation/git-credential.txt b/Documentation/git-credential.txt
index e70ff89..a81684e 100644
--- a/Documentation/git-credential.txt
+++ b/Documentation/git-credential.txt
@@ -64,12 +64,20 @@ infomation it has):
2. Ask git-credential to give us a username and password for this
description. This is done by running `git credential fill`,
- feeding the description from step (1) to its standard input. The
- credential will be produced on standard output, like:
+ feeding the description from step (1) to its standard input. The complete
+ credential description (including the credential per se, i.e. the
+ login and password) will be produced on standard output, like:
+ protocol=https
+In most cases, this means the attributes given in the input will be
+repeated in the output, but git may also modify the credential
+description, for example by removing the `path` attribute when the
+protocol is HTTP(s) and `credential.useHttpPath` is false.
If the `git credential` knew about the password, this step may
not have involved the user actually typing this password (the
user may have typed a password to unlock the keychain instead,
@@ -86,8 +94,8 @@ unlocked) before it returned `password=secr3t`.
was rejected during the operation, use the "reject" action so
that `git credential` will ask for a new password in its next
invocation. In either case, `git credential` should be fed with
- the credential description obtained from step (2) together with
- the ones already provided in step (1).
+ the credential description obtained from step (2) (which also
+ contain the ones provided in step (1)).