{"full_name":"git-ecosystem/git-credential-manager","owner":"git-ecosystem","name":"git-credential-manager","shard":"1","url":"https://github.com/git-ecosystem/git-credential-manager","description":"Secure, cross-platform Git credential storage with authentication to GitHub, Azure Repos, and other popular Git hosting services.","homepage":"","topics":["git","credential","github","azure-repos","azure-devops","authentication","aad","bitbucket","cross-platform","gitlab"],"tag_pages":["authentication","bitbucket","cross-platform","git","github","gitlab"],"language":"C#","license":"NOASSERTION","avatar":"https://avatars.githubusercontent.com/u/64464614?v=4","created_at":"2018-11-20T14:50:07Z","pushed_at":"2026-11-10T14:26:39Z","metrics":{"stars":9452,"forks":2979,"watchers":353,"issues":909,"prs":1032,"releases":61,"issues_open":135,"issues_closed":774,"prs_open":21,"prs_closed":266,"prs_merged":745,"discussions":65},"growth":{"day":{"stars":7,"forks":1,"base_day":"2026-11-15"}},"history":{"dates":["2026-11-10","2026-11-11","2026-11-12","2026-11-13","2026-11-14","2026-11-15","2026-11-16"],"stars":[9439,9445,9448,9447,9447,9445,9452],"forks":[2972,2975,2978,2979,2979,2978,2979],"watchers":[null,353,353,353,353,353,353],"issues_open":[null,134,134,134,135,135,135],"prs_open":[null,20,21,21,21,21,21]},"boards":{},"same_owner":[],"issues":[{"number":1555,"title":"Constant popups to authenticate HTTP(S) access to the remote repository","comments":32,"created_at":"2024-03-21T14:33:16Z"},{"number":1408,"title":"GCM OAuth Issue - GCM Erases Expired Token But Does Not Renew - Gitea","comments":29,"created_at":"2023-09-11T16:44:30Z"},{"number":694,"title":"When using the Secret Service credential store, if the keyring is locked at the time when I run a Git operation then GCM deletes the credential from the keyring and fails to authenticate with the remote","comments":21,"created_at":"2022-05-12T08:34:43Z"},{"number":1775,"title":"OAuth2 authentication fails once after access_token expired.  ","comments":16,"created_at":"2024-11-22T12:09:33Z"},{"number":2319,"title":"Authentication flow repeated on each git action","comments":12,"created_at":"2026-04-15T08:25:01Z"},{"number":1813,"title":"Bug: GCM Misidentifies Docker Containers Running on WSL2 Due to /proc/version","comments":12,"created_at":"2025-01-27T07:48:06Z"},{"number":2194,"title":"git-credential-manager prompting to auth with GitHub when running git git fetch","comments":11,"created_at":"2025-11-26T12:20:55Z"},{"number":1705,"title":"GCM does not prompt for auth on first git call after PATs expire","comments":10,"created_at":"2024-09-19T21:22:05Z"}],"discussions":[{"number":2494,"title":"(spam)","comments":0,"category":"Ideas","created_at":"2026-10-31T21:41:26Z"},{"number":2452,"title":"use raw data in credential stores and API","comments":1,"category":"Ideas","created_at":"2026-09-18T23:29:27Z"},{"number":2447,"title":"Gitlab and GCM with SSO","comments":0,"category":"General","created_at":"2026-09-16T23:26:31Z"},{"number":2392,"title":"FR: Narrowly-scoped, TTL and/or password based access to the store","comments":0,"category":"Ideas","created_at":"2026-07-20T09:44:50Z"},{"number":2359,"title":"How to configure gcm so that you need to enter a password every session?","comments":3,"category":"Q&A","created_at":"2026-06-20T03:30:12Z"},{"number":2306,"title":"(spam)","comments":1,"category":"Q&A","created_at":"2026-04-03T00:56:20Z"},{"number":2093,"title":"PDM","comments":2,"category":"General","created_at":"2025-10-30T11:41:51Z"},{"number":2060,"title":"Missing Repository Context in GCM OAuth Login Prompts","comments":5,"category":"General","created_at":"2025-09-27T09:23:51Z"}],"latest_release":{"name":"GCM 3.0.2","tag":"v3.0.2","published_at":"2026-10-26T11:48:13Z","body":"Git Credential Manager 3.0 brings native ahead-of-time compilation, Microsoft authentication broker support across Windows, macOS, and Linux, and a refreshed terminal experience.\r\n\r\n**Security Fixes:**\r\n\r\n- Binaries now use the .NET Runtime 10.0.14 which has [fixes for CVE-2026-111497](https://github.com/dotnet/announcements/issues/494) regarding Brotli HTTP decompression.\r\n\r\n> [!NOTE]\r\n> Analysis of GCM shows that Brotli HTTP compression is **not** enabled by default across any version, so there is no real-world impact.\r\n\r\n# Changes since 3.0.1\r\n\r\n- Dependency updates (#2483)\r\n- Documentation updates for AI agents (#2469)\r\n- Official release pipeline signing fixes, and update to use the new Mac pool (#2467, #2468)\r\n- Fix for Linux SecretService credential MIME type (#2475)\r\n- Allow headless use of Linux SecretService (#2474)\r\n\r\n**Changelog:** [v3.0.1...v3.0.2][point2-changelog]\r\n\r\n# Changes since 3.0.0\r\n\r\n- **(Bug fix)** Prompt for default OS account on Microsoft DevBox (#2459)\r\n- **(Bug fix)** Restore Entra broker parent window handling (#2464)\r\n- **(Feature)** Support `authtype` Git capability (#2457)\r\n- **(Feature)** Add console parent window parenting for non-Entra UI (#2465)\r\n- Drop Windows x86 release binaries (#2456)\r\n\r\n**Changelog:** [v3.0.0...v3.0.1][point1-changelog]\r\n\r\n# Changes since 2.9.1\r\n\r\n> [!IMPORTANT]\r\n> This release changes supported operating systems and the default Azure Repos authentication experience. Review the breaking changes before upgrading.\r\n\r\n## Breaking changes and upgrade notes\r\n\r\n### Updated platform and .NET requirements\r\n\r\nGCM now targets **.NET 10 on all platforms**. Windows builds no longer use .NET Framework.\r\n\r\n| Platform or installation method | Requirement |\r\n| --- | --- |\r\n| Windows | Windows 10 or later; Windows Server 2016 or later |\r\n| macOS | macOS 14 or later |\r\n| Linux | A distribution supported by .NET 10 |\r\n| .NET tool | Install the .NET 10 SDK before installing or updating GCM |\r\n\r\nSee the [supported environments][supported-environments] and [.NET 10 support matrix][dotnet-support] for details. Standalone platform packages do **not** require a separate .NET installation.\r\n\r\n**Windows 7 and Windows 8.x are no longer supported by GCM 3.x.** GCM 2.9.x will receive minimal, security-only maintenance for those systems, but no new features. Upgrading Windows is recommended. ([git-ecosystem/git-credential-manager#2365][pr-2365], [git-ecosystem/git-credential-manager#2367][pr-2367])\r\n\r\n### Azure Repos uses OAuth tokens by default\r\n\r\nGCM now returns Microsoft identity **OAuth tokens**, rather than creating personal access tokens (PATs), by default for Azure Repos. OAuth tokens are automatically refreshed as needed.\r\n\r\nExplicit credential-type settings are still respected. If you need the previous PAT behavior, set:\r\n\r\n```shell\r\ngit config --global credential.azreposCredentialType pat\r\n```\r\n\r\nThe equivalent environment variable is `GCM_AZREPOS_CREDENTIALTYPE=pat`. See [Azure Repos users and tokens][azrepos-tokens]. ([git-ecosystem/git-credential-manager#2449][pr-2449])\r\n\r\n### Microsoft authentication uses the OS broker by default\r\n\r\nBroker integration is now enabled by default wherever supported, rather than requiring an opt-in. This applies to Microsoft authentication, such as Azure Repos; it does not change authentication for GitHub, Bitbucket, or GitLab.\r\n\r\nOn macOS, broker authentication requires Company Portal and device enrollment. On Linux, it requires the supported Intune setup, a GNOME desktop, and Microsoft Edge; headless and WSL environments do not support the Linux broker.\r\n\r\n> [!WARNING]\r\n> Depending on your organization's policies, broker sign-in can prompt you to join or enroll your device. On Windows, signing in with a personal Microsoft account can also affect the account linked to your local Windows user. Review the [broker documentation][broker] before proceeding, especially on personal devices.\r\n\r\nTo opt out:\r\n\r\n```shell\r\ngit config --global credential.msauthUseBrok","is_prerelease":false},"readme":true,"readme_zh":false,"news":[],"stale":false,"snapshot_at":"2026-11-16T09:23:14Z","history_start":"2026-09-06"}