Cheatsheet50 commands9 groupsClick to copy

50 Git commands Cheatsheet

The Git commands you will use every day, grouped by what they do. Copy any command with one click, and see where it moves your files.

⭐ MOST USED: START WITH THESEPick a command to see what it does

git status

Shows which files you changed, which are staged and which Git is not tracking yet. It never changes anything.

ReadsWorking folder and Staging area

USE IT WHEN

Before every add and commit, so you know exactly what you are about to save.

💡 TIP

Run it often. It is the safest command in Git.

git add .

Puts every change in the current folder into the staging area, ready for the next commit.

MovesWorking folder → Staging area

USE IT WHEN

Everything you changed belongs in the same commit.

💡 TIP

Want only one file? Use git add <file> instead.

git commit -am "<message>"

Stages changes to files Git already tracks and saves them as one commit with your message, in a single step.

SavesWorking folder → Local repository

USE IT WHEN

Quick saves on files you have committed before.

💡 TIP

Brand new files are skipped. Run git add on them first.

git push -u origin main

Sends the commits on your local main branch to GitHub. The -u flag links main to origin/main.

SendsLocal repository → Remote (GitHub)

USE IT WHEN

You want your commits on GitHub. Add -u on the first push only.

💡 TIP

After the first push, plain git push is enough.

git clone <url>

Downloads a full copy of a repository, with its whole history, into a new folder on your computer.

CopiesRemote (GitHub) → Working folder

USE IT WHEN

You start working on a project that already exists on GitHub.

💡 TIP

Copy the URL from the green Code button on the repository page.

git init

Creates a hidden .git folder, so Git starts tracking this folder as a new repository.

CreatesLocal repository

USE IT WHEN

Once, at the start of a brand new project.

💡 TIP

Cloned projects already have a .git folder. Do not run it again there.

git log --oneline

Lists your commits, newest first, with a short ID and the message on each line.

ReadsLocal repository

USE IT WHEN

You need a commit ID or want a quick look at recent history.

💡 TIP

If the list is long, press q to leave it.

git branch

Lists your local branches. The one marked with * is the branch you are on.

ReadsLocal repository

USE IT WHEN

Before you switch to or create a branch.

💡 TIP

Add -a to see remote branches too.

git checkout <branch-name>

Switches to another branch and updates the files in your working folder to match it.

UpdatesLocal repository → Working folder

USE IT WHEN

You want to work on, or look at, a different branch.

💡 TIP

Commit or stash your changes first. git switch <branch-name> does the same job.

git diff

Shows, line by line, what you changed in your files but have not staged yet.

ReadsWorking folder

USE IT WHEN

Before git add, to review your own changes.

💡 TIP

Already staged? Use git diff --staged.

1 of 10

Understanding Git: Adding the Files to Git

Git moves your changes through four places. Most commands just move files from one place to the next. Click a place to see the commands that work there.

Tip: git add moves files to staging, git commit saves them to your local repo, git push sends them to GitHub.

All Git commands

Pick any command on the left to see what it does, where it moves your files and when to use it. The copy icon copies it straight away. Advanced commands sit at the end of the list.

50 of 50 commands

BASIC COMMANDS5

GIT COMMITS4

CHECKING LOGS AND VIEWS5

GIT DIFF3

RENAME AND REMOVE FILES2

WORKING WITH BRANCHES7

UNDO CHANGES6

ADDING CHANGES TO REMOTE5

ADVANCED COMMANDS13

Basic commands

git init

Creates a hidden .git folder, so Git starts tracking this folder as a new repository.

CreatesLocal repository

USE IT WHEN

Once, at the start of a brand new project.

💡 TIP

Cloned projects already have a .git folder. Do not run it again there.

Basic commands

git add .

Puts every change in the current folder into the staging area, ready for the next commit.

MovesWorking folder → Staging area

USE IT WHEN

Everything you changed belongs in the same commit.

💡 TIP

Want only one file? Use git add <file> instead.

Basic commands

git add <file>

Puts the changes from one file into the staging area. Other changed files stay where they are.

MovesWorking folder → Staging area

USE IT WHEN

You want to commit some of your changes, not all of them.

💡 TIP

Stage several files at once: git add a.txt b.txt

Basic commands

git add -A

Stages every change in the whole repository: new, edited and deleted files, even outside the folder you are in.

MovesWorking folder → Staging area

USE IT WHEN

You want everything in the next commit.

💡 TIP

git add . covers only the current folder. -A covers the whole repository.

Basic commands

git clone <url>

Downloads a full copy of a repository, with its whole history, into a new folder on your computer.

CopiesRemote (GitHub) → Working folder

USE IT WHEN

You start working on a project that already exists on GitHub.

💡 TIP

Copy the URL from the green Code button on the repository page.

Git commits

git commit

Saves everything in the staging area as a new commit. Git opens your text editor so you can write the message.

SavesStaging area → Local repository

USE IT WHEN

You staged your changes and want to write a longer message.

💡 TIP

Add -m "your message" to skip the editor.

Git commits

git commit -a

Stages every change to files Git already tracks and commits it. Git opens your editor for the message.

SavesWorking folder → Local repository

USE IT WHEN

Quick commits when you have not created any new files.

💡 TIP

New, untracked files are not included. Run git add on them first.

Git commits

git commit -am "<message>"

Stages changes to files Git already tracks and saves them as one commit with your message, in a single step.

SavesWorking folder → Local repository

USE IT WHEN

Quick saves on files you have committed before.

💡 TIP

Brand new files are skipped. Run git add on them first.

Git commits⚠ Careful: can delete work

git commit --amend -m "<message>"

Replaces your last commit with a new one that has this message, plus anything you have staged.

RewritesStaging area and Local repository

USE IT WHEN

You spotted a typo in the last message or forgot to add a file.

💡 TIP

Only amend commits you have not pushed. It changes the commit ID.

Checking logs and views

git log

Lists every commit on the current branch, newest first, with the author, date and full message.

ReadsLocal repository

USE IT WHEN

You want the full history of the branch.

💡 TIP

Scroll with the arrow keys. Press q to leave.

Checking logs and views

git log --summary

Shows the commit history plus a note of the files each commit created, deleted or renamed.

ReadsLocal repository

USE IT WHEN

You want to find when a file was added or removed.

💡 TIP

For the number of changed lines per file, try git log --stat.

Checking logs and views

git log --oneline

Lists your commits, newest first, with a short ID and the message on each line.

ReadsLocal repository

USE IT WHEN

You need a commit ID or want a quick look at recent history.

💡 TIP

If the list is long, press q to leave it.

Checking logs and views

git status

Shows which files you changed, which are staged and which Git is not tracking yet. It never changes anything.

ReadsWorking folder and Staging area

USE IT WHEN

Before every add and commit, so you know exactly what you are about to save.

💡 TIP

Run it often. It is the safest command in Git.

Checking logs and views

git show

Shows your latest commit: its message, author and the exact lines it changed.

ReadsLocal repository

USE IT WHEN

You want to see what one commit did.

💡 TIP

See an older commit with git show <commit-sha>.

Git diff

git diff

Shows, line by line, what you changed in your files but have not staged yet.

ReadsWorking folder

USE IT WHEN

Before git add, to review your own changes.

💡 TIP

Already staged? Use git diff --staged.

Git diff

git diff --color-words

Works like git diff, but highlights only the words that changed instead of whole lines.

ReadsWorking folder

USE IT WHEN

Reviewing small edits in long lines, such as docs or Markdown.

💡 TIP

Handy for blog posts and README files.

Git diff

git diff --staged

Shows the changes you have staged, which is exactly what your next commit will contain.

ReadsStaging area

USE IT WHEN

Right before git commit, as a final check.

💡 TIP

git diff --cached does the same thing.

Rename and remove files

git mv <filename> <new-filename>

Renames the file in your folder and stages the rename, in one step.

RenamesWorking folder → Staging area

USE IT WHEN

You want to rename a file Git already tracks.

💡 TIP

It moves files too: git mv a.txt docs/a.txt

Rename and remove files⚠ Careful: can delete work

git rm <filename>

Deletes the file from your folder and stages the deletion for the next commit.

DeletesWorking folder → Staging area

USE IT WHEN

A tracked file is no longer needed.

💡 TIP

Want to keep the file on disk? Use git rm --cached <filename>.

Working with branches

git branch

Lists your local branches. The one marked with * is the branch you are on.

ReadsLocal repository

USE IT WHEN

Before you switch to or create a branch.

💡 TIP

Add -a to see remote branches too.

Working with branches

git branch <name>

Creates a new branch that points at your current commit. You stay on the branch you are on.

CreatesLocal repository

USE IT WHEN

You want to start new work without touching main.

💡 TIP

git switch -c <name> creates it and switches to it in one step.

Working with branches⚠ Careful: can delete work

git branch -d <branch-name>

Deletes a local branch. Git refuses if the branch has commits you have not merged yet.

DeletesLocal repository

USE IT WHEN

A branch is merged and you are done with it.

💡 TIP

-D forces the delete. Use it only if you are sure.

Working with branches

git checkout <branch-name>

Switches to another branch and updates the files in your working folder to match it.

UpdatesLocal repository → Working folder

USE IT WHEN

You want to work on, or look at, a different branch.

💡 TIP

Commit or stash your changes first. git switch <branch-name> does the same job.

Working with branches

git switch <branch-name>

Switches to another branch and updates your files to match. It only handles branches, so it is harder to misuse than checkout.

UpdatesLocal repository → Working folder

USE IT WHEN

Everyday branch switching on Git 2.23 or newer.

💡 TIP

git switch - jumps back to the branch you were on before.

Working with branches

git merge <branch-name>

Brings the commits from another branch into the branch you are on.

CombinesLocal repository

USE IT WHEN

Your feature branch is ready to join main.

💡 TIP

Switch to the branch that should receive the changes first.

Working with branches

git merge --abort

Stops a merge that hit conflicts and puts your branch and files back the way they were before it.

CancelsWorking folder and Local repository

USE IT WHEN

A merge goes wrong and you want to start over.

💡 TIP

Works only while the merge is still in progress.

Undo changes⚠ Careful: can delete work

git checkout -- <file>

Throws away your unstaged changes to one file and restores its last staged or committed version.

DiscardsStaging area → Working folder

USE IT WHEN

You broke a file and want it back as it was.

💡 TIP

Newer Git: git restore <file> does the same.

Undo changes⚠ Careful: can delete work

git checkout -- .

Throws away every unstaged change in the current folder.

DiscardsStaging area → Working folder

USE IT WHEN

You want a clean slate and do not need your edits.

💡 TIP

There is no undo. Run git stash first if you are unsure.

Undo changes

git reset HEAD <file>

Takes a file out of the staging area. Your edits stay in the file.

UnstagesStaging area → Working folder

USE IT WHEN

You staged a file by mistake.

💡 TIP

Newer Git: git restore --staged <file> does the same.

Undo changes

git revert <commit-sha>

Makes a new commit that does the opposite of an earlier one. History is kept and nothing is deleted.

CreatesLocal repository

USE IT WHEN

Undoing a commit that is already pushed and shared.

💡 TIP

Safe on shared branches, unlike reset.

Undo changes

git clean -n

Lists the untracked files that git clean -f would delete. It deletes nothing.

ReadsWorking folder

USE IT WHEN

Every time, before you run git clean -f.

💡 TIP

Add -d to include untracked folders.

Undo changes⚠ Careful: can delete work

git clean -f

Permanently deletes untracked files from your folder. They do not go to the bin.

DeletesWorking folder

USE IT WHEN

Build output or junk files are cluttering your folder.

💡 TIP

Run git clean -n first to preview.

Adding changes to remote

git remote add origin <url>

Saves the GitHub URL under the name origin, so your local repository knows where to push.

ConnectsLocal repository and Remote (GitHub)

USE IT WHEN

Once, after git init and before your first push.

💡 TIP

Check it with git remote -v.

Adding changes to remote

git branch -M main

Renames your current branch to main, even if a branch called main already exists.

RenamesLocal repository

USE IT WHEN

Your repository started on master and you want main, like GitHub.

💡 TIP

-m does the same but refuses to overwrite an existing branch.

Adding changes to remote

git push -u origin main

Sends the commits on your local main branch to GitHub. The -u flag links main to origin/main.

SendsLocal repository → Remote (GitHub)

USE IT WHEN

You want your commits on GitHub. Add -u on the first push only.

💡 TIP

After the first push, plain git push is enough.

Adding changes to remote

git fetch

Downloads new commits from GitHub into your local repository, without touching your files or branches.

DownloadsRemote (GitHub) → Local repository

USE IT WHEN

You want to see what others pushed before you merge it.

💡 TIP

Then compare with git log HEAD..origin/main

Adding changes to remote

git pull

Fetches new commits and merges them into your current branch, which updates your files.

DownloadsRemote (GitHub) → Working folder

USE IT WHEN

At the start of the day, and before you push.

💡 TIP

Commit or stash your local changes first to avoid conflicts.

Advanced commands

git stash

Saves your uncommitted changes in a hidden stash and resets your folder to the last commit.

StashesWorking folder → Local repository

USE IT WHEN

You need to switch branches but are not ready to commit.

💡 TIP

Add -u to stash untracked files too.

Advanced commands

git stash list

Lists every stash you have saved, newest first, as stash@{0}, stash@{1} and so on.

ReadsLocal repository

USE IT WHEN

You have stashed more than once and lost track.

💡 TIP

See what is inside one: git stash show -p stash@{0}

Advanced commands

git stash pop

Puts your latest stashed changes back into your folder and removes them from the stash list.

RestoresLocal repository → Working folder

USE IT WHEN

You are back on the branch and ready to carry on.

💡 TIP

git stash apply restores the changes but keeps the stash, just in case.

Advanced commands⚠ Careful: can delete work

git rebase <branch-name>

Takes your commits and replays them on top of another branch, so history reads as one straight line.

RewritesLocal repository

USE IT WHEN

Updating your feature branch with the latest main before a pull request.

💡 TIP

Never rebase commits that other people have already pulled.

Advanced commands⚠ Careful: can delete work

git rebase -i HEAD~<n>

Opens a list of your last n commits where you can squash, reword, reorder or drop them.

RewritesLocal repository

USE IT WHEN

Tidying up messy commits before you push.

💡 TIP

Change pick to squash to fold a commit into the one above it.

Advanced commands

git cherry-pick <commit-sha>

Takes one commit from any branch and applies it as a new commit on the branch you are on.

CopiesLocal repository

USE IT WHEN

You need one fix from another branch, not the whole branch.

💡 TIP

Get the commit ID from git log --oneline.

Advanced commands

git reset --soft HEAD~1

Removes your last commit but keeps all of its changes staged, ready to commit again.

UndoesLocal repository → Staging area

USE IT WHEN

You committed too early or with the wrong message.

💡 TIP

Use it only on commits you have not pushed.

Advanced commands⚠ Careful: can delete work

git reset --hard <commit-sha>

Moves your branch back to that commit and wipes every later commit and every uncommitted change.

DiscardsWorking folder and Staging area and Local repository

USE IT WHEN

You are certain you want to throw work away.

💡 TIP

Lost something? git reflog can usually find it.

Advanced commands

git reflog

Lists every commit HEAD has pointed to, including commits no branch shows any more.

ReadsLocal repository

USE IT WHEN

After a bad reset or rebase, to find a lost commit.

💡 TIP

Rescue a lost commit with git branch <name> <commit-sha>.

Advanced commands⚠ Careful: can delete work

git push --force-with-lease

Replaces the remote branch with your local one, but stops if someone else pushed since your last fetch.

OverwritesLocal repository → Remote (GitHub)

USE IT WHEN

After a rebase or amend on a branch only you work on.

💡 TIP

Safer than --force. Never force push to main.

Advanced commands

git tag -a <tag> -m "<message>"

Adds a named label with a message to the current commit, usually a release such as v1.0.0.

CreatesLocal repository

USE IT WHEN

You ship a release.

💡 TIP

Tags are not pushed by default. Use git push origin <tag>.

Advanced commands

git blame <file>

Shows each line of a file next to the commit, author and date that last changed it.

ReadsLocal repository

USE IT WHEN

You want to know when or why a line changed.

💡 TIP

Every file on GitHub has a Blame button too.

Advanced commands

git bisect start

Starts a binary search. You mark commits as good or bad and Git narrows down the one that added the bug.

SearchesLocal repository

USE IT WHEN

Something broke and you do not know which commit did it.

💡 TIP

Finish with git bisect reset to return to your branch.

1 of 50

KEY

Working folderStaging areaLocal repoRemote

Can delete work<orange> Your own value

<file> Replace the part in orange with your own value. ⚠ Careful Can delete work. Read before running.

Watch the video

Conclusion

Bookmark this page and come back whenever you need a command. In the next lesson you will create your first GitHub repository.

UP NEXTCreate GitHub Repo (GUI)

TAGGED

Share this page

MAINTAINED BY

Sanjay Viswanathan

@sanjay-kv

Founder of recodehive and Technical program manager, Prev Google ML Facilitator & Ex- GitHub CE who delivered 100+ talks on ML and open source and developer advocacy.

View profile Follow

Was this helpful?

Your vote helps us improve our docs.

Improve this page

All our docs are open source. Found a typo, want to add detail or have a better explanation? Anyone can contribute.

Edit on GitHub Contributing guidelines

Understanding Git: Adding the Files to Git​

All Git commands​

Watch the video

Conclusion​

Sanjay Viswanathan

Comments

Understanding Git: Adding the Files to Git

All Git commands

Conclusion