Git Commands Reference

Overview

A searchable Git command reference with 38 commands grouped into categories from setup and staging through branching, merging, stashing, remotes, tags, undo, and advanced archaeology like bisect and blame. Each command carries a plain-English description and a one-click copy button.

How It Works

Type into the search box to filter commands by name, description, or category — matching commands regroup instantly. Each row shows the command in monospace with its description beneath; press Copy to place the exact command text on your clipboard. When nothing matches, the page says so explicitly rather than showing an empty screen. The reference is static data shipped with the page, so it works offline and loads with no delay.

Step-by-Step Usage Guide

1. Search for a task ('undo', 'branch', 'remote') rather than a command name if you are unsure.
2. Read the description to confirm the command does what you expect.
3. Copy the command with one click.
4. Paste it into your terminal and adapt any placeholder arguments.

Technical Specifications & Standards

The command list is curated for the commands people actually fumble: staging subtleties (git add -p for interactive hunk staging), the commit fix-ups (--amend), history reading (log --graph --oneline, shortlog -sn), branch management including the modern git switch, stash workflows, remote hygiene (fetch versus pull, push --force-with-lease as the safe force-push), annotated versus lightweight tags, and the undo ladder — reset --soft to keep changes staged, reset --hard with an explicit destructive warning, and revert as the shared-branch-safe option. Descriptions carry the safety-relevant context inline rather than in footnotes, which is why the destructive commands are labelled as such in the list itself. The tool is a reference, not a shell: commands are copied for you to run in your own terminal, and nothing here executes Git or touches your repositories. Two scope notes: it covers the standard Git command line — no plumbing commands, aliases, or host-specific workflows like pull requests — and the list is fixed in the page rather than user-editable.

Targeted Use Cases

• Looking up the safe force-push flag before updating a shared branch.
• Recalling the difference between reset --soft, reset --hard, and revert.
• Finding the interactive staging command while assembling a clean commit.
• Onboarding teammates by sharing a copy-ready command list.

Notes & Gotchas

• Prefer revert over reset --hard on any branch other people build on.
• Read the inline warnings on destructive commands before copying them.
• Replace placeholder arguments like <url> or <name> with your real values after pasting.
• Use the search rather than scrolling — the categories are also filter targets.

Frequently Asked Questions