Git Reference Library
1 model · 50 error codes
Browse the current Git reference family: repository states, push rejections, history warnings, transport failures, and local metadata messages.
About Git Error Reference
Git communicates errors through human-readable messages rather than numeric codes. These messages cover repository state issues (such as detached HEAD or unmerged paths), push rejections (non-fast-forward, protected branch), history warnings (divergent branches, shallow clone limitations), and transport failures (authentication, network timeouts).
Because Git messages are descriptive rather than encoded, understanding them requires context about which Git operation produced the message and what repository state triggered it. FixerCode organizes Git messages by operational family, making it easier to find related messages that share the same root cause or workflow stage.
FixerCode documents 50 Git messages across 1 model, grouped by message family: repository states, push rejections, history warnings, transport failures, and local metadata issues. Each entry explains what the message means, why Git produces it, and how it relates to other Git states in the same workflow.
Select The Git Message Family 1
Frequently Asked Questions
Git was designed for human-readable output. Instead of numeric codes, Git produces descriptive messages that explain the problem in context. This makes errors easier to understand directly but requires organizing them by operational family for structured reference.
A non-fast-forward rejection means the remote branch has commits that your local branch does not have. Pushing would overwrite those commits, so Git blocks the push until you pull and merge or rebase first.
Git messages are grouped by operational family: repository states, push rejections, history warnings, transport failures, and local metadata issues. Each family covers a different stage of the Git workflow, making it easier to find related messages.