# Git "Password authentication is no longer supported" in CI

> Fix the GitHub "Support for password authentication was removed" CI error by switching HTTPS Git from an account password to a personal access or App token.

Source: https://latchkey.dev/learn/git/git-password-authentication-removed-in-ci  
Updated: 2026-06-26

GitHub removed account-password authentication for Git over HTTPS. A pipeline still passing a password is rejected outright and must use a token instead.

## Diagnose it: depth, refs, or credentials?

```Terminal
git rev-parse --is-shallow-repository
git rev-parse --abbrev-ref HEAD    # prints HEAD when detached
git log --oneline -3
git remote -v
```

> `actions/checkout` fetches depth 1 on a detached HEAD. Anything diffing against a base, reading a branch name, or running `git describe` needs `fetch-depth: 0`.

## FAQ

### What causes Git "Password authentication is no longer supported" in CI?

There are 2 common causes: account password used for https git and cached old credentials. A legacy script or stored credential still sends the GitHub account password, which is no longer accepted.

### How do I fix Git "Password authentication is no longer supported" in CI?

There are 2 fixes depending on which cause you have: authenticate with a token and clear stale cached credentials. Work through them in order, since the first is the most common.

### What does Git "Password authentication is no longer supported" in CI actually mean?

A clone or push over HTTPS fails with remote: Support for password authentication was removed.

### How do I stop Git "Password authentication is no longer supported" in CI happening again?

Switch all HTTPS Git auth to tokens (PAT, App, or the workflow GITHUB_TOKEN), and never store an account password in CI.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt