Skip to content

Commit 5ed190b

Browse files
authored
Merge pull request #383 from microsoft/vtbassmatt-patch-1
a small "how to use" tweak
2 parents 8b585a2 + 65f753c commit 5ed190b

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

README.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -144,8 +144,11 @@ To uninstall, open Control Panel and navigate to the Programs and Features scree
144144

145145
## How to use
146146

147-
Git Credential Manager Core is called implicitly by Git, when so configured. It is not intended to be called directly by the user.
148-
For example, when pushing (`git push`) to [Azure DevOps](https://dev.azure.com), a window is automatically opened and an OAuth2 flow is started to get your personal access token.
147+
Once it's installed and configured, Git Credential Manager Core is called implicitly by Git.
148+
You don't have to do anything special, and GCM Core isn't intended to be called directly by the user.
149+
For example, when pushing (`git push`) to [Azure DevOps](https://dev.azure.com), [Bitbucket](https://bitbucket.org), or [GitHub](https://github.com), a window will automatically open and walk you through the sign-in process.
150+
(This process will look slightly different for each Git host, and even in some cases, whether you've connected to an on-premises or cloud-hosted Git host.)
151+
Later Git commands in the same repository will re-use existing credentials or tokens that GCM Core has stored for as long as they're valid.
149152

150153
Read full command line usage [here](docs/usage.md).
151154

0 commit comments

Comments
 (0)