Lessley Dennington
Lessley Dennington
GCM currently ignores ports in URIs. This means adding a URI with a port to your config will not result in the expected behavior (e.g. shortcutting the provider auto-detect process...
Allow users to install/uninstall the new `arm64` package via Homebrew by: 1. Updating the `uninstall.sh` script to use the correct Homebrew prefix for arm64. Tested locally with `brew uninstall` and...
Add basic installer validation to release pipeline for Windows, macOS (x64 only), and Linux (Debian package only). Validation runs the installers/any necessary setup and `git-credential-manager-core --version`. Test run validating these...
**Feature description** The default `HOMEBREW_PREFIX` is `/usr/local` on non-Apple silicon machines, and our macOS scripts assume that GCM will be installed in the `\share` sub-directory located in this path. However,...
**Note:** This is more of a request for help with a specific scenario than a bug. In light of that, if there's somewhere better for me to direct this request,...
GCM is currently published to a [private tap](https://github.com/microsoft/homebrew-git). However, in an effort to standardize macOS installs, we plan to migrate it to the official Homebrew tap (`Homebrew/homebrew-core`). We are taking...
Update GCM to detect when it is running in a CI environment and use the appropriate token(s) for authentication. For the initial iteration, this effort will be scoped to GitHub...
Today GCM's [`postinstall`](https://github.com/GitCredentialManager/git-credential-manager/blob/main/src/osx/Installer.Mac/scripts/postinstall) script, which runs after the macOS installer to create symlinks, install Homebrew (if needed), etc. is something of a black box. This lack of visibility makes it...
The current implementation of Trace2 regions in GCM only supports top-level regions (i.e. no nesting). Since [Git supports nesting](https://git-scm.com/docs/api-trace2#Documentation/technical/api-trace2.txt-coderegionentercode), GCM should as well for feature parity.
For the initial Trace2 implementation, we used `main` as the thread name in all messages. This should be updated to capture different thread names in multi-threaded scenarios, as described [here](https://git-scm.com/docs/api-trace2#Documentation/technical/api-trace2.txt-codeltthread-namegtcode).