Skip to content

Git Credential Manager (windows 11)

On Windows 11, Git Credential Manager (GCM) can make your Git workflow smoother, more secure, and less error‑prone — especially if you work across multiple repos and hosting services like GitHub, Azure DevOps, Bitbucket, or GitLab.

What is GCM?

Git Credential Manager is a secure, cross‑platform credential helper for Git. It handles authentication to Git hosting services (GitHub, Azure DevOps, Bitbucket, GitLab, etc.) without requiring you to manually enter credentials every time.

It replaces older helpers like wincred and git-credential-store with modern, secure, and user‑friendly authentication flows.

Info

This applies to using HTTPS connections to Git but is not part if you use SSH keys

The Problem Without GCM

  • Git over HTTPS prompts for credentials on every push/pull unless you store them.
  • Storing passwords in plain text (git-credential-store) is insecure.
  • Many services now require personal access tokens (PATs) or OAuth with MFA — not supported by older helpers.

The Solution: GCM

  • Stores credentials securely in the OS keychain (Windows Credential Manager, macOS Keychain, Linux Secret Service).
  • Supports modern authentication flows (OAuth, PATs, MFA).
  • Works consistently across platforms and Git hosts.

How It Works

  1. Trigger — You run a Git command over HTTPS that needs authentication (git clone, git push, etc.).
  2. Intercept — Git calls the configured credential helper (GCM).
  3. Authenticate — GCM launches a sign‑in flow:
    • Opens a browser or native dialog for OAuth.
    • Prompts for PAT if OAuth isn’t available.
    • Store Securely — Credentials are encrypted and saved in the OS credential vault.
  4. Reuse — On subsequent Git operations, GCM retrieves and supplies credentials automatically.

Supported Git Hosts

  • GitHub — OAuth, PAT, MFA
  • Azure DevOps — OAuth, PAT, MFA, Windows Integrated Auth
  • Bitbucket — OAuth, App Passwords
  • GitLab — OAuth, PAT