Editorial policy

One question, answered first

Each page answers one practical question in its opening paragraph, then shows the complete example and the evidence behind the answer. Every page ends with what it does not cover and its sources.

Commands are checked and run

Every command, option and behaviour we describe is checked against the official Git documentation for the pinned release. Every printed example ran in a fresh, fictional repository, and the printed code is byte-identical to the script that ran. When Git changes behaviour in a new release, we re-run the examples and say what changed.

Warnings before risk

Anything that rewrites history or discards work carries a clear warning before the command, both in the guides and in the explorer. We say what a recovery method can and cannot bring back, and we never promise to recover work that was never committed or records that have expired.

Limits are stated

A guide describes the conditions it ran under: local text files, the pinned Git release and a fictional repository. Shared history, hosted services, other operating systems and other releases are named as limits rather than assumed to behave the same way.

Original work only

Explanations, examples, records and code are written new for this site. We do not reuse code, command data, text or designs from earlier projects at this domain or from other references.

AI assistance and responsibility

Pages are written by AI systems working from the sources and runs above and checked against them before publication. The publisher directs the work and is responsible for every page: errors are corrected in public as described in corrections.

Review

Independent review by a named Git educator and version-control engineer is being added. A reviewed page shows the reviewer’s name, credential and review date. Reviewers must be independent of any sponsor on the page.