Clarification on new GCM GitHub OAuth authorizations

[garretwilson]

Could you provide more documentation with clarification on what is going on with this new GCM GitHub OAuth authorization, particularly on Windows 10?

Historically GCM has used the Windows 10 credential manager to store Git passwords, I believe. Today I upgraded to Git for Windows 2.30.2.windows.1. When I did a git push to GitHub, it took me to the GitHub page for me to authorize Git Credential Manager. Then my git push succeeded.

Familiar with basic OAuth workflows, I infer that rather than storing my GitHub password in the Windows 10 credential manager, GCM will now use GitHub OAuth to get some sort of authorization token, which it will store locally and use for authentication until it expires.

Do I understand that part correctly? (Maybe you could give a quick overview of that somewhere in the intro documentation?)

If so, then so far so good. When I go to https://github.com/settings/applications I see under "Authorized OAuth Apps" the listing "Git Credential Manager".

But what happens when I access GitHub from multiple computers? Will I have multiple "Git Credential Manager" authorizations listed? How will I know which of them belong to which computer? Will I be able to add names the authorizations in order to tell them apart? Do they already have the device name somewhere that I haven't found?