sxyazi/yazi · error

`git` command failed: {status}

Error message

`git` command failed: {status}

What it means

Generic status guard at the end of git command execution (`exec`): the git subprocess ran to completion but returned a non-zero exit status. The specific git subcommand is opaque here; consult the preceding `.args()` and git's stderr for the real cause (network failure, bad ref, permission error, etc.).

Source

Thrown at yazi-cli/src/package/git.rs:115

			"-c",
			"core.eol=lf",
			"-c",
			"core.autocrlf=false",
			"-c",
			"core.symlinks=false",
			"-c",
			"clone.defaultRemoteName=origin",
			"-c",
			"checkout.defaultRemote=origin",
			"-c",
			"advice.detachedHead=false",
		]))
		.status()
		.await
		.context("Failed to execute `git` command")?;

		if !status.success() {
			bail!("`git` command failed: {status}");
		}

		Ok(())
	}
}

View on GitHub (pinned to 5f901b886b)

Solutions

1. Re-run the same git command manually to see its stderr output.
2. Check network access and credentials for remote operations (clone/fetch).
3. Ensure the refs requested (e.g. origin/HEAD) exist in the repository.

When it happens

Trigger: Thrown at yazi-cli/src/package/git.rs:115 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of sxyazi/yazi@5f901b886b (2026-09-02). Data as JSON: /api/errors/754159e1a25ffe7c. Report an issue: GitHub.