Git Docs

Git answers drift with new commands and changing flag defaults, and blur into hosting-provider docs, so ground each answer in the live docs at https://git-scm.com/docs/, not memory, and link the exact page behind every claim.

Route GitHub Actions to github-actions-docs, and GitLab merge requests or CI/CD pipelines to gitlab-ci-docs. Other GitHub features (pull requests, GitHub CLI, repository settings) belong to GitHub's own docs, and GUI clients to their own docs, unless the question turns on the underlying Git command.

Workflow

1. Locate the question in references/topic-map.md, a selective index of docs entry points. Done when each part of the question maps to a section of the map, or you have noted that none fits.
2. Search git-scm.com with the user's exact terms plus Git vocabulary such as --force-with-lease, ORIG_HEAD, reflog, fast-forward, detached HEAD, or ancestry path, starting from the map's pages and the Routing rules below. Done when you hold the one page that most directly answers each part.
3. Read each page down to the relevant section. Done when you have read the passage behind every claim you will make. When a page has moved, been renamed, or stops short, say so and link the nearest authoritative pages.
4. Answer with the direct answer first, each docs link beside the claim it supports, and commands only when the user asks or the page needs them. Mark any conclusion that joins several pages as Inference:. Done when every claim cites a specific page, not the docs home.

Routing