profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/vtbassmatt/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Matt Cooper vtbassmatt GitHub North Carolina, United States

microsoft/typed-rest-client 562

Node Rest and Http Clients with typings for use with TypeScript

MicrosoftDocs/azure-devops-docs 488

This repo is the home of the official Azure DevOps documentation for Microsoft. GitHub Issues filed in this repository should be for problems with the documentation.

microsoft/azure-devops-dotnet-samples 416

.NET/C# samples for integrating with Azure DevOps Services and Azure DevOps Server

microsoft/vsts-agent-docker 189

(Deprecated) VSTS agent Docker images

vtbassmatt/django-expression-fields 17

django-expression-fields lets your users type a mathematical expression in a form field. Python does the math and stores the result in the database.

vtbassmatt/django-drynk 14

DRY Natural Keys for Django

vtbassmatt/azf-wsgi 11

Azure Functions + WSGI

vtbassmatt/ci-comparo 3

Running multiple hosted CIs in one project

vtbassmatt/devshots-pipeline-template-tactics 3

Examples from Feb 2021 DevSHOTS talk

vtbassmatt/ba.dg.es 2

Display badges from various social networks

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add DPAPI based credential store on Windows

-# Credential stores on Linux+# Credential stores -There are four options for storing credentials that Git Credential-Manager Core (GCM Core) manages on Linux platforms:+There are several options for storing credentials that GCM Core supports: -1. [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)-2. GPG/[`pass`](https://www.passwordstore.org/) compatible files-3. Git's built-in [credential cache](https://git-scm.com/docs/git-credential-cache)-4. Plaintext files+- Windows Credential Manager+- macOS Keychain+- [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)+- GPG/[`pass`](https://www.passwordstore.org/) compatible files+- Git's built-in [credential cache](https://git-scm.com/docs/git-credential-cache)+- Plaintext files -By default, GCM Core comes unconfigured. After running `git-credential-manager-core configure`, you can select which credential store-to use by setting the [`GCM_CREDENTIAL_STORE`](environment.md#GCM_CREDENTIAL_STORE)+The default credential stores on macOS and Windows are the macOS Keychain and+the Windows Credential Manager, respectively.++GCM comes without a default store on Linux distributions.++You can select which credential store to use by setting the [`GCM_CREDENTIAL_STORE`](environment.md#GCM_CREDENTIAL_STORE) environment variable, or the [`credential.credentialStore`](configuration.md#credentialcredentialstore) Git configuration setting.  Some credential stores have limitations, or further configuration required-depending on your particular setup.+depending on your particular setup. See more detailed information below for each+credential store.++## Windows Credential Manager++**Available on:** _Windows_++**This is the default store on Windows.**++**:warning: Does not work over a network/SSH session.**++```batch+SET GCM_CREDENTIAL_STORE="wincredman"+``` -## 1. [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)+or  ```shell-export GCM_CREDENTIAL_STORE=secretservice+git config --global credential.credentialStore wincredman+```++This credential store uses the Windows Credential APIs (`wincred.h`) to store+data securely in the Windows Credential Manager (also known as the Windows+Credential Vault in earlier versions of Windows).++You can [access and manage data in the credential manager](https://support.microsoft.com/en-us/windows/accessing-credential-manager-1b5c916a-6a16-889f-8581-fc16e8165ac0)+from the control panel, or via the [`cmdkey` command-line tool](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/cmdkey).++When connecting to a Windows machine over a network session (such as SSH), GCM+is unable to persist credentials to the Windows Credential Manager due to+limitations in Windows itself. Note that connecting by Remote Desktop does not+suffer from the same limitation.++## DPAPI protected files++**Available on:** _Windows_++```batch+SET GCM_CREDENTIAL_STORE="dpapi"+```++or++```shell+git config --global credential.credentialStore dpapi+```++This credential store uses Windows DPAPI to encrypt credentials which are stored+as files in your file system. The file structure is the same as the+[plaintext files credential store](#plaintext-files) except the first line (the+secret value) is protected by DPAPI.++By default files are stored in `~/.gcm/dpapi_store` but this can be configured using

🤔 since this is a Windows-only feature, it's slightly strange to offer the directory path in Unixy format.

mjcheetham

comment created time in 3 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add DPAPI based credential store on Windows

-# Credential stores on Linux+# Credential stores -There are four options for storing credentials that Git Credential-Manager Core (GCM Core) manages on Linux platforms:+There are several options for storing credentials that GCM Core supports: -1. [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)-2. GPG/[`pass`](https://www.passwordstore.org/) compatible files-3. Git's built-in [credential cache](https://git-scm.com/docs/git-credential-cache)-4. Plaintext files+- Windows Credential Manager+- macOS Keychain+- [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)+- GPG/[`pass`](https://www.passwordstore.org/) compatible files+- Git's built-in [credential cache](https://git-scm.com/docs/git-credential-cache)+- Plaintext files -By default, GCM Core comes unconfigured. After running `git-credential-manager-core configure`, you can select which credential store-to use by setting the [`GCM_CREDENTIAL_STORE`](environment.md#GCM_CREDENTIAL_STORE)+The default credential stores on macOS and Windows are the macOS Keychain and+the Windows Credential Manager, respectively.++GCM comes without a default store on Linux distributions.++You can select which credential store to use by setting the [`GCM_CREDENTIAL_STORE`](environment.md#GCM_CREDENTIAL_STORE) environment variable, or the [`credential.credentialStore`](configuration.md#credentialcredentialstore) Git configuration setting.  Some credential stores have limitations, or further configuration required-depending on your particular setup.+depending on your particular setup. See more detailed information below for each+credential store.++## Windows Credential Manager++**Available on:** _Windows_++**This is the default store on Windows.**++**:warning: Does not work over a network/SSH session.**++```batch+SET GCM_CREDENTIAL_STORE="wincredman"+``` -## 1. [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)+or  ```shell-export GCM_CREDENTIAL_STORE=secretservice+git config --global credential.credentialStore wincredman+```++This credential store uses the Windows Credential APIs (`wincred.h`) to store+data securely in the Windows Credential Manager (also known as the Windows+Credential Vault in earlier versions of Windows).++You can [access and manage data in the credential manager](https://support.microsoft.com/en-us/windows/accessing-credential-manager-1b5c916a-6a16-889f-8581-fc16e8165ac0)+from the control panel, or via the [`cmdkey` command-line tool](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/cmdkey).++When connecting to a Windows machine over a network session (such as SSH), GCM+is unable to persist credentials to the Windows Credential Manager due to+limitations in Windows itself. Note that connecting by Remote Desktop does not

Consider: due to limitations in Windows. Connecting by Remote Desktop doesn't suffer from this limitation.

mjcheetham

comment created time in 3 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add DPAPI based credential store on Windows

 Permissions on existing directories will not be modified.  --- -<p align="center">- :warning: **WARNING** :warning:  **This storage mechanism is NOT secure!** -**Secrets and credentials are stored in plaintext files _without any security_!<br/>-Git Credential Manager Core takes no liability for the safety of these-credentials.**+**Secrets and credentials are stored in plaintext files _without any security_!**++**Git Credential Manager Core takes no liability for the safety of these credentials.**

This is an odd disclaimer. Consider replacing with "We strongly advise against using GCM Core in this configuration" or something like that.

mjcheetham

comment created time in 3 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add DPAPI based credential store on Windows

-# Credential stores on Linux+# Credential stores -There are four options for storing credentials that Git Credential-Manager Core (GCM Core) manages on Linux platforms:+There are several options for storing credentials that GCM Core supports: -1. [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)-2. GPG/[`pass`](https://www.passwordstore.org/) compatible files-3. Git's built-in [credential cache](https://git-scm.com/docs/git-credential-cache)-4. Plaintext files+- Windows Credential Manager+- macOS Keychain+- [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)+- GPG/[`pass`](https://www.passwordstore.org/) compatible files+- Git's built-in [credential cache](https://git-scm.com/docs/git-credential-cache)+- Plaintext files -By default, GCM Core comes unconfigured. After running `git-credential-manager-core configure`, you can select which credential store-to use by setting the [`GCM_CREDENTIAL_STORE`](environment.md#GCM_CREDENTIAL_STORE)+The default credential stores on macOS and Windows are the macOS Keychain and+the Windows Credential Manager, respectively.++GCM comes without a default store on Linux distributions.++You can select which credential store to use by setting the [`GCM_CREDENTIAL_STORE`](environment.md#GCM_CREDENTIAL_STORE) environment variable, or the [`credential.credentialStore`](configuration.md#credentialcredentialstore) Git configuration setting.  Some credential stores have limitations, or further configuration required-depending on your particular setup.+depending on your particular setup. See more detailed information below for each+credential store.++## Windows Credential Manager++**Available on:** _Windows_++**This is the default store on Windows.**++**:warning: Does not work over a network/SSH session.**++```batch+SET GCM_CREDENTIAL_STORE="wincredman"+``` -## 1. [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)+or  ```shell-export GCM_CREDENTIAL_STORE=secretservice+git config --global credential.credentialStore wincredman+```++This credential store uses the Windows Credential APIs (`wincred.h`) to store+data securely in the Windows Credential Manager (also known as the Windows+Credential Vault in earlier versions of Windows).++You can [access and manage data in the credential manager](https://support.microsoft.com/en-us/windows/accessing-credential-manager-1b5c916a-6a16-889f-8581-fc16e8165ac0)+from the control panel, or via the [`cmdkey` command-line tool](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/cmdkey).++When connecting to a Windows machine over a network session (such as SSH), GCM+is unable to persist credentials to the Windows Credential Manager due to+limitations in Windows itself. Note that connecting by Remote Desktop does not+suffer from the same limitation.++## DPAPI protected files++**Available on:** _Windows_++```batch+SET GCM_CREDENTIAL_STORE="dpapi"+```++or++```shell+git config --global credential.credentialStore dpapi+```++This credential store uses Windows DPAPI to encrypt credentials which are stored+as files in your file system. The file structure is the same as the+[plaintext files credential store](#plaintext-files) except the first line (the+secret value) is protected by DPAPI.++By default files are stored in `~/.gcm/dpapi_store` but this can be configured using

Also, consider breaking into two sentences. By default, files are stored in <place>. This can be configured...

mjcheetham

comment created time in 3 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add DPAPI based credential store on Windows

-# Credential stores on Linux+# Credential stores -There are four options for storing credentials that Git Credential-Manager Core (GCM Core) manages on Linux platforms:+There are several options for storing credentials that GCM Core supports: -1. [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)-2. GPG/[`pass`](https://www.passwordstore.org/) compatible files-3. Git's built-in [credential cache](https://git-scm.com/docs/git-credential-cache)-4. Plaintext files+- Windows Credential Manager+- macOS Keychain+- [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)+- GPG/[`pass`](https://www.passwordstore.org/) compatible files+- Git's built-in [credential cache](https://git-scm.com/docs/git-credential-cache)+- Plaintext files -By default, GCM Core comes unconfigured. After running `git-credential-manager-core configure`, you can select which credential store-to use by setting the [`GCM_CREDENTIAL_STORE`](environment.md#GCM_CREDENTIAL_STORE)+The default credential stores on macOS and Windows are the macOS Keychain and+the Windows Credential Manager, respectively.++GCM comes without a default store on Linux distributions.++You can select which credential store to use by setting the [`GCM_CREDENTIAL_STORE`](environment.md#GCM_CREDENTIAL_STORE) environment variable, or the [`credential.credentialStore`](configuration.md#credentialcredentialstore) Git configuration setting.  Some credential stores have limitations, or further configuration required-depending on your particular setup.+depending on your particular setup. See more detailed information below for each+credential store.++## Windows Credential Manager++**Available on:** _Windows_++**This is the default store on Windows.**++**:warning: Does not work over a network/SSH session.**++```batch+SET GCM_CREDENTIAL_STORE="wincredman"+``` -## 1. [freedesktop.org Secret Service API](https://specifications.freedesktop.org/secret-service/)+or  ```shell-export GCM_CREDENTIAL_STORE=secretservice+git config --global credential.credentialStore wincredman+```++This credential store uses the Windows Credential APIs (`wincred.h`) to store+data securely in the Windows Credential Manager (also known as the Windows+Credential Vault in earlier versions of Windows).++You can [access and manage data in the credential manager](https://support.microsoft.com/en-us/windows/accessing-credential-manager-1b5c916a-6a16-889f-8581-fc16e8165ac0)+from the control panel, or via the [`cmdkey` command-line tool](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/cmdkey).++When connecting to a Windows machine over a network session (such as SSH), GCM+is unable to persist credentials to the Windows Credential Manager due to+limitations in Windows itself. Note that connecting by Remote Desktop does not+suffer from the same limitation.++## DPAPI protected files++**Available on:** _Windows_++```batch+SET GCM_CREDENTIAL_STORE="dpapi"+```++or++```shell+git config --global credential.credentialStore dpapi+```++This credential store uses Windows DPAPI to encrypt credentials which are stored+as files in your file system. The file structure is the same as the+[plaintext files credential store](#plaintext-files) except the first line (the+secret value) is protected by DPAPI.++By default files are stored in `~/.gcm/dpapi_store` but this can be configured using+the environment variable `GCM_DPAPI_STORE_PATH` environment variable.++If the directory does not exist is will be created.

Typo: s/is/it/

Nit: s/does not/doesn't/

mjcheetham

comment created time in 3 days

PullRequestReviewEvent
PullRequestReviewEvent
GollumEvent

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add support for using WSL Git for configuration

+# Windows Subsystem for Linux (WSL)++Git Credential Manager Core can be used with the [Windows Subsystem for Linux+(WSL)](https://aka.ms/wsl) to enable secure authentication of your remote Git+repositories from inside of WSL.++## Supported versions++GCM Core supports being called from both WSL1 and WSL2 installations.++**Note:** In order to use GCM with WSL, _without_ a Git for Windows installation+you must be using GCM version 2.0.XXX or later.+You must also be on Windows 10 Version 1903 and later. This is the first version+of Windows that includes the required `wsl.exe` command-line tool that GCM uses+to interoperate with Git in your WSL distributions.++## Set up WSL & Git Credential Manager

Also this header uses some form of the verb "set up" whose name I don't know, while the section below starts with the gerund form of "using". Would be clearer if they both used the same verb tense.

mjcheetham

comment created time in 4 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add support for using WSL Git for configuration

+# Windows Subsystem for Linux (WSL)++Git Credential Manager Core can be used with the [Windows Subsystem for Linux+(WSL)](https://aka.ms/wsl) to enable secure authentication of your remote Git+repositories from inside of WSL.++## Supported versions++GCM Core supports being called from both WSL1 and WSL2 installations.++**Note:** In order to use GCM with WSL, _without_ a Git for Windows installation+you must be using GCM version 2.0.XXX or later.+You must also be on Windows 10 Version 1903 and later. This is the first version+of Windows that includes the required `wsl.exe` command-line tool that GCM uses+to interoperate with Git in your WSL distributions.++## Set up WSL & Git Credential Manager++### Step 1++[Install the latest Git for Windows ⬇️](https://github.com/git-for-windows/git/releases/latest)++### Step 2++_Inside your WSL installation_, run the following command to set GCM as the Git+credential helper:++```shell+git config --global credential.helper /mnt/c/Program\ Files/Git/mingw64/libexec/git-core/git-credential-manager-core.exe+```++### Step 3 (Azure DevOps only)++If you intend to use Azure DevOps you must _also_ set the following Git+configuration _inside of your WSL installation_.++```shell+git config --global credential.https://dev.azure.com.useHttpPath true+```++## Using GCM & WSL without Git for Windows++If you wish to use GCM Core inside of WSL _without installing Git for Windows_+you must complete additional configuration so that GCM can callback to Git+inside of your WSL installation.++In **_Windows_** you need to update the `WSLENV` environment variable to include+the value `GIT_EXEC_PATH/wp`. From an _Administrator_ Command Prompt run the+following:++```batch+SETX WSLENV=%WSLENV%:GIT_EXEC_PATH/wp+```++..and then restart your WSL installation.++## How it works++GCM leverages the built-in interoperability between Windows and WSL, provided by+Microsoft. You can read more about Windows/WSL interop [here](https://docs.microsoft.com/en-us/windows/wsl/interop).++Git inside of a WSL installation can launch the GCM _Windows_ application+transparently to acquire credentials. Running GCM as a Windows application+allows it to take full advantage of the host operating system for storing+credentials securely, and presenting GUI prompts for authentication.++By using the host operating system (Windows) to store credentials also means+that your Windows applications and WSL distributions can all share those+credentials, removing the need to sign-in multiple times.++## Caveats

Maybe call this "important note about configuration settings" or something more direct than simply "caveats".

mjcheetham

comment created time in 4 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add support for using WSL Git for configuration

+# Windows Subsystem for Linux (WSL)++Git Credential Manager Core can be used with the [Windows Subsystem for Linux+(WSL)](https://aka.ms/wsl) to enable secure authentication of your remote Git+repositories from inside of WSL.++## Supported versions++GCM Core supports being called from both WSL1 and WSL2 installations.++**Note:** In order to use GCM with WSL, _without_ a Git for Windows installation+you must be using GCM version 2.0.XXX or later.+You must also be on Windows 10 Version 1903 and later. This is the first version+of Windows that includes the required `wsl.exe` command-line tool that GCM uses+to interoperate with Git in your WSL distributions.++## Set up WSL & Git Credential Manager

Missing a "with Git for Windows" in the header maybe?

mjcheetham

comment created time in 4 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add support for using WSL Git for configuration

+# Windows Subsystem for Linux (WSL)++Git Credential Manager Core can be used with the [Windows Subsystem for Linux+(WSL)](https://aka.ms/wsl) to enable secure authentication of your remote Git+repositories from inside of WSL.++## Supported versions++GCM Core supports being called from both WSL1 and WSL2 installations.++**Note:** In order to use GCM with WSL, _without_ a Git for Windows installation+you must be using GCM version 2.0.XXX or later.+You must also be on Windows 10 Version 1903 and later. This is the first version+of Windows that includes the required `wsl.exe` command-line tool that GCM uses+to interoperate with Git in your WSL distributions.++## Set up WSL & Git Credential Manager++### Step 1++[Install the latest Git for Windows ⬇️](https://github.com/git-for-windows/git/releases/latest)++### Step 2++_Inside your WSL installation_, run the following command to set GCM as the Git+credential helper:++```shell+git config --global credential.helper /mnt/c/Program\ Files/Git/mingw64/libexec/git-core/git-credential-manager-core.exe+```++### Step 3 (Azure DevOps only)++If you intend to use Azure DevOps you must _also_ set the following Git+configuration _inside of your WSL installation_.++```shell+git config --global credential.https://dev.azure.com.useHttpPath true+```++## Using GCM & WSL without Git for Windows++If you wish to use GCM Core inside of WSL _without installing Git for Windows_+you must complete additional configuration so that GCM can callback to Git+inside of your WSL installation.++In **_Windows_** you need to update the `WSLENV` environment variable to include+the value `GIT_EXEC_PATH/wp`. From an _Administrator_ Command Prompt run the+following:++```batch+SETX WSLENV=%WSLENV%:GIT_EXEC_PATH/wp+```++..and then restart your WSL installation.

I would either omit the ellipsis or make it a full, three-dotted ellipsis.

mjcheetham

comment created time in 4 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add support for using WSL Git for configuration

+# Windows Subsystem for Linux (WSL)++Git Credential Manager Core can be used with the [Windows Subsystem for Linux+(WSL)](https://aka.ms/wsl) to enable secure authentication of your remote Git+repositories from inside of WSL.++## Supported versions++GCM Core supports being called from both WSL1 and WSL2 installations.++**Note:** In order to use GCM with WSL, _without_ a Git for Windows installation+you must be using GCM version 2.0.XXX or later.+You must also be on Windows 10 Version 1903 and later. This is the first version+of Windows that includes the required `wsl.exe` command-line tool that GCM uses+to interoperate with Git in your WSL distributions.++## Set up WSL & Git Credential Manager++### Step 1++[Install the latest Git for Windows ⬇️](https://github.com/git-for-windows/git/releases/latest)++### Step 2++_Inside your WSL installation_, run the following command to set GCM as the Git+credential helper:++```shell+git config --global credential.helper /mnt/c/Program\ Files/Git/mingw64/libexec/git-core/git-credential-manager-core.exe+```++### Step 3 (Azure DevOps only)++If you intend to use Azure DevOps you must _also_ set the following Git+configuration _inside of your WSL installation_.++```shell+git config --global credential.https://dev.azure.com.useHttpPath true+```++## Using GCM & WSL without Git for Windows++If you wish to use GCM Core inside of WSL _without installing Git for Windows_+you must complete additional configuration so that GCM can callback to Git+inside of your WSL installation.++In **_Windows_** you need to update the `WSLENV` environment variable to include+the value `GIT_EXEC_PATH/wp`. From an _Administrator_ Command Prompt run the+following:++```batch+SETX WSLENV=%WSLENV%:GIT_EXEC_PATH/wp+```++..and then restart your WSL installation.++## How it works++GCM leverages the built-in interoperability between Windows and WSL, provided by+Microsoft. You can read more about Windows/WSL interop [here](https://docs.microsoft.com/en-us/windows/wsl/interop).++Git inside of a WSL installation can launch the GCM _Windows_ application+transparently to acquire credentials. Running GCM as a Windows application+allows it to take full advantage of the host operating system for storing+credentials securely, and presenting GUI prompts for authentication.++By using the host operating system (Windows) to store credentials also means

I think the leading "By" is incorrect grammar, and can be safely dropped.

mjcheetham

comment created time in 4 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add support for using WSL Git for configuration

+# Windows Subsystem for Linux (WSL)++Git Credential Manager Core can be used with the [Windows Subsystem for Linux+(WSL)](https://aka.ms/wsl) to enable secure authentication of your remote Git+repositories from inside of WSL.++## Supported versions++GCM Core supports being called from both WSL1 and WSL2 installations.++**Note:** In order to use GCM with WSL, _without_ a Git for Windows installation

I might frame this differently for greater clarity. Something more like, "To use GCM with WSL, you either need a Git for Windows installation or to be using GCM 2.0.XXX+. Under all circumstances, you must be using Windows 10 version 1903 or later. That version of Windows introduced wsl.exe which is required for GCM to work with Git on WSL."

(I don't love my exact wording in this suggestion, feel free to tweak. The core point is to replace the somewhat convoluted "To use this without that you need this other".)

mjcheetham

comment created time in 4 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add support for using WSL Git for configuration

+# Windows Subsystem for Linux (WSL)++Git Credential Manager Core can be used with the [Windows Subsystem for Linux

Suggestion:

GCM Core can be used with the [Windows Subsystem for Linux (WSL)](https://aka.ms/wsl), both WSL1 and WSL2, by following these instructions.

Then drop the "to enable secure..." part, the ## Supported versions header, and the first sentence of that section. The reader picks back up at the **Note:**.

mjcheetham

comment created time in 4 days

Pull request review commentmicrosoft/Git-Credential-Manager-Core

Add support for using WSL Git for configuration

 To uninstall, open the Settings app and navigate to the Apps section. Select "Gi  To uninstall, open Control Panel and navigate to the Programs and Features screen. Select "Git Credential Manager Core" and click "Remove". +#### Windows Subsystem for Linux (WSL)++Git Credential Manager Core can be used with the [Windows Subsystem for Linux+(WSL)](https://aka.ms/wsl) to enable secure authentication of your remote Git+repositories from inside of WSL.++Please read [here](docs/wsl.md) for information.

Suggestion: something more like [Please see the GCM Core on WSL docs](docs/wsl.md) for more information. I suspect this helps mildly with SEO, screenreaders, and so on.

mjcheetham

comment created time in 4 days

PullRequestReviewEvent
PullRequestReviewEvent

push eventmicrosoft/Git-Credential-Manager-Core

Matt Cooper

commit sha 22d474b99e551a2122b2e0b1b81b070ae50b8789

Update codeql-analysis.yml

view details

push time in 14 days

pull request commentmicrosoft/Git-Credential-Manager-Core

Add CodeQL scanning

I would remove the commented-out lines, and the code comments that are talking about languages other than C#.

I will definitely clean this up before merging. Thanks!

vtbassmatt

comment created time in 14 days

pull request commentmicrosoft/Git-Credential-Manager-Core

Add CodeQL scanning

We seem to be ✅ clean from a CodeQL standpoint. It's the longest-running CI check at 6 minutes, though, so perhaps we don't want to put this in the PR path.

vtbassmatt

comment created time in 15 days

push eventmicrosoft/Git-Credential-Manager-Core

Matt Cooper

commit sha cf2b9ddac7657f0e4d80192ec54a9b14f6314f00

Update codeql-analysis.yml

view details

push time in 15 days

push eventmicrosoft/Git-Credential-Manager-Core

Matt Cooper

commit sha 78f2e37f3c3caab078dd6049b4dccaea80cd61fc

remove autobuild

view details

push time in 15 days

delete branch microsoft/Git-Credential-Manager-Core

delete branch : lgtm

delete time in 15 days

create barnchmicrosoft/Git-Credential-Manager-Core

branch : codeql

created branch time in 15 days

create barnchmicrosoft/Git-Credential-Manager-Core

branch : lgtm

created branch time in 15 days

delete branch microsoft/Git-Credential-Manager-Core

delete branch : hubbify

delete time in 22 days