From 50a9a80042a1c01274edcc9886683f1a69ccc8cf Mon Sep 17 00:00:00 2001 From: Matthew John Cheetham Date: Tue, 2 Mar 2021 11:38:06 +0000 Subject: [PATCH] azrepos: mark credmode option as experimental Mark the Azure Repos credential mode option as experimental whilst we iron out some of the bugs and UX. --- docs/azrepos-users-and-tokens.md | 6 +++--- docs/configuration.md | 4 ++-- docs/environment.md | 4 ++-- docs/usage.md | 2 +- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/azrepos-users-and-tokens.md b/docs/azrepos-users-and-tokens.md index c01761cacc..a4bf386ab4 100644 --- a/docs/azrepos-users-and-tokens.md +++ b/docs/azrepos-users-and-tokens.md @@ -5,7 +5,7 @@ The Azure Repos host provider supports creating multiple types of credential: - Personal Access Token -- Azure Access Token +- Azure Access Token (experimental) ### Personal Access Tokens @@ -19,7 +19,7 @@ PATs have a limited lifetime and new tokens must be created once they expire. In Git Credential Manager, when a PAT expired (or was manually revoked) this resulted in a new authentication prompt. -### Azure Access Tokens +### Azure Access Tokens (experimental) Azure Access Tokens is the generic term for tokens issued by Azure Active Directory for either Work and School Accounts (AAD tokens) or Personal Accounts @@ -37,7 +37,7 @@ including the Visual Studio IDE and Azure CLI. This means that as long as you're using Git or one of these tools with the same account, you'll never need to re-authenticate due to expired tokens! -## User Accounts +## User Accounts (experimental) In versions of Git Credential Manager that support Azure Access Tokens, the user account used to authenticate for a particular Azure DevOps organization will now diff --git a/docs/configuration.md b/docs/configuration.md index fea7947685..d47bda3e70 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -336,7 +336,7 @@ Credential: "git:https://bob@github.com/example/myrepo" (user = bob) --- -### credential.azreposCredentialType +### credential.azreposCredentialType _(experimental)_ Specify the type of credential the Azure Repos host provider should return. @@ -355,4 +355,4 @@ More information about Azure Access tokens can be found [here](azrepos-azuretoke git config --global credential.azreposCredentialType azure ``` -**Also see: [GCM_AZREPOS_CREDENTIALTYPE](environment.md#GCM_AZREPOS_CREDENTIALTYPE)** +**Also see: [GCM_AZREPOS_CREDENTIALTYPE](environment.md#GCM_AZREPOS_CREDENTIALTYPE-experimental)** diff --git a/docs/environment.md b/docs/environment.md index 42eef7b1d1..f3ebd0db5d 100644 --- a/docs/environment.md +++ b/docs/environment.md @@ -427,7 +427,7 @@ export GCM_MSAUTH_FLOW="devicecode" --- -### GCM_AZREPOS_CREDENTIALTYPE +### GCM_AZREPOS_CREDENTIALTYPE _(experimental)_ Specify the type of credential the Azure Repos host provider should return. @@ -452,4 +452,4 @@ SET GCM_AZREPOS_CREDENTIALTYPE="false" export GCM_AZREPOS_CREDENTIALTYPE="false" ``` -**Also see: [credential.azreposCredentialType](configuration.md#azreposcredentialtype)** +**Also see: [credential.azreposCredentialType](configuration.md#azreposcredentialtype-experimental)** diff --git a/docs/usage.md b/docs/usage.md index 9a17622439..701163f96e 100644 --- a/docs/usage.md +++ b/docs/usage.md @@ -31,7 +31,7 @@ Set your user-level Git configuration (`~/.gitconfig`) to use GCM Core. If you p `--system` to these commands, they act on the system-level Git configuration (`/etc/gitconfig`) instead. -### azure-repos +### azure-repos (experimental) Interact with the Azure Repos host provider to bind/unbind user accounts to Azure DevOps organizations or specific remote URLs, and manage the authentication authority cache.