A quick reference for one common Git task
Selecting the 'commit' task returns the standard three-command sequence: git add -A, git commit -m "message", and git status -- stage all changes, commit them with a message, then confirm the working tree is clean.
git add -A stages all changes (new, modified, and deleted files) across the entire repository, which is more sweeping than git add . in older Git versions (which historically only staged changes within the current directory) -- worth knowing since it affects exactly what gets included in the next commit.
Running git status after the commit isn't strictly required for the commit to succeed, but it's included here as a verification habit -- confirming the working tree is clean after committing catches the case where you intended to stage everything but something was left out.
Why this covers common tasks, not destructive ones
Cheat sheet text. Destructive resets are not included. This tool is scoped to safe, commonly needed command sequences (like committing, branching, or checking status) -- deliberately excluding destructive operations like git reset --hard, git push --force, or git clean -f, which can permanently discard work if used incorrectly and shouldn't be copy-pasted without understanding exactly what they do first.
git add -A stages everything indiscriminately, including files you might not have intended to commit -- for more selective staging, git add
This is a static reference for the named task -- it doesn't inspect your actual repository state (uncommitted changes, current branch, remote status), so the exact commands relevant to your specific situation may need adjustment beyond this generic sequence.
Related developer reference and safety tools
For a similar quick-reference lookup on Unix file permissions instead of Git commands, the Unix chmod Octal Calculator serves the same kind of fast reference need.
Frequently Asked Questions (FAQ)
Why git add -A instead of git add .?
git add -A stages all changes across the entire repository (new, modified, and deleted files everywhere), while git add . historically only staged changes within the current directory and below in older Git versions -- -A is the more comprehensive, repository-wide staging command.
Is running git status after committing necessary?
Not strictly required for the commit itself to succeed, but it's a useful verification habit included here to confirm the working tree is clean afterward -- catching cases where something intended for the commit was accidentally left unstaged.
Why doesn't this tool include commands like git reset --hard?
Cheat sheet text. Destructive resets are not included. Commands that can permanently discard uncommitted work (like a hard reset or force push) are deliberately excluded from this quick-reference tool, since they carry real risk if copy-pasted without fully understanding their effect first.
Does this account for my repository's actual current state?
No. This is a static, generic command sequence for the selected task -- it doesn't inspect your actual repository (current branch, existing changes, remote configuration), so you may need to adjust the exact commands for your specific situation.
What if I only want to stage one specific file instead of everything?
Use git add
