Need help with github-cheat-sheet?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

33.4K Stars 5.0K Forks MIT License 505 Commits 16 Opened issues


A list of cool features of Git and GitHub.

Services available


Need anything else?

Contributors list

GitHub Cheat Sheet Awesome

A collection of cool hidden and not so hidden features of Git and GitHub. This cheat sheet was inspired by Zach Holman's Git and GitHub Secrets talk at Aloha Ruby Conference 2012 (slides) and his More Git and GitHub Secrets talk at WDCNZ 2013 (slides).


Read this in other languages: English, 한국어, 日本語, 简体中文, 正體中文.

Table of Contents


Ignore Whitespace


to any diff URL will remove any changes only in whitespace, enabling you to see only the code that has changed.

Diff without whitespace

Read more about GitHub secrets.

Adjust Tab Space


to a diff or file URL will display tab characters as 4 spaces wide instead of the default 8. The number after
can be adjusted to suit your preference. This does not work on Gists, or raw file views, but a Chrome extension can automate this.

Here is a Go source file before adding


Before, tab space example

...and this is after adding


After, tab space example

Commit History by Author

To view all commits on a repo by author add

to the URL.

DHH commit history

Read more about the differences between commits views.

Cloning a Repository

When cloning a repository the

can be left off the end.
$ git clone

Read more about the Git



Compare all Branches to Another Branch

If you go to the repo's Branches page, next to the Commits button:{user}/{repo}/branches

... you would see a list of all branches which are not merged into the main branch.

From here you can access the compare page or delete a branch with a click of a button.

Compare branches not merged into master in rails/rails repo -

Comparing Branches

To use GitHub to compare branches, change the URL to look like this:{user}/{repo}/compare/{range}


{range} = master...4-1-stable

For example:

Rails branch compare example

can be changed to things like:[email protected]{}...master[email protected]{2014-10-04}...master

Here, dates are in the format


Another compare example

Branches can also be compared in


Read more about comparing commits across time.

Compare Branches across Forked Repositories

To use GitHub to compare branches across forked repositories, change the URL to look like this:{user}/{repo}/compare/{foreign-user}:{branch}...{own-branch}

For example:

Forked branch compare


Gists are an easy way to work with small bits of code without creating a fully fledged repository.



to the end of any Gist URL (like this) in order to get the HTML-only version suitable for embedding in any other site.

Gists can be treated as a repository so they can be cloned like any other:

$ git clone


This means you also can modify and push updates to Gists:

$ git commit
$ git push
Username for '':
Password for 'https://[email protected]':

However, Gists do not support directories. All files need to be added to the repository root. Read more about creating Gists. is a simple URL shortener for GitHub.

You can also use it via pure HTTP using Curl:

$ curl -i -F "url="
HTTP/1.1 201 Created

$ curl -i HTTP/1.1 302 Found Location:

Read more about

Keyboard Shortcuts

When on a repository page, keyboard shortcuts allow you to navigate easily.

  • Pressing
    will bring up a file explorer.
  • Pressing
    will bring up the branch selector.
  • Pressing
    will focus the search field for the current repository. Pressing ↓ to select the “All GitHub” option changes the field to search all of GitHub.
  • Pressing
    will edit labels on existing Issues.
  • Pressing
    when looking at a file (e.g.,
    ) will change your URL to one which, in effect, freezes the page you are looking at. If this code changes, you will still be able to see what you saw at that current time.

To see all of the shortcuts for the current page press


Keyboard shortcuts

Read more about search syntax you can use.

Line Highlighting in Repositories

Either adding, e.g.,

to the end of a code file URL or simply clicking the line number will highlight that line number.

It also works with ranges, e.g.,

, to select ranges, hold
and click two lines:

Line Highlighting

Closing Issues via Commit Messages

If a particular commit fixes an issue, any of the keywords

, followed by the issue number, will close the issue once it is committed to the repository's default branch.
$ git commit -m "Fix screwup, fixes #12"

This closes the issue and references the closing commit.

Closing Repo

Read more about closing Issues via commit messages.

Cross-Link Issues

If you want to link to another issue in the same repository, simply type hash

then the issue number, and it will be auto-linked.

To link to an issue in another repository,

, e.g.,

Cross-Link Issues

Locking Conversations

Pull Requests and Issues can now be locked by owners or collaborators of the repo.

Lock conversation

This means that users who are not collaborators on the project will no longer be able to comment.

Comments locked

Read more about locking conversations.

CI Status on Pull Requests

If set up correctly, every time you receive a Pull Request, Travis CI will build that Pull Request just like it would every time you make a new commit. Read more about how to get started with Travis CI.

Travis CI status

Read more about the commit status API.


Both issues and pull requests allow filtering in the user interface.

For the Rails repo:, the following filter is built by selecting the label "activerecord":

is:issue label:activerecord

But, you can also find all issues that are NOT labeled activerecord:

is:issue -label:activerecord

Additionally, this also works for pull requests:

is:pr -label:activerecord

Github has tabs for displaying open or closed issues and pull requests but you can also see merged pull requests. Just put the following in the filter:


Read more about searching issues.

Finally, github now allows you to filter by the Status API's status.

Pull requests with only successful statuses:


Read more about searching on the Status API.

Syntax Highlighting in Markdown Files

For example, to syntax highlight Ruby code in your Markdown files write:

require 'tabbit'
table ='Name', 'Email')
table.add_row('Tim Green', '[email protected]')
puts table.to_s

This will produce:

require 'tabbit'
table ='Name', 'Email')
table.add_row('Tim Green', '[email protected]')
puts table.to_s

GitHub uses Linguist to perform language detection and syntax highlighting. You can find out which keywords are valid by perusing the languages YAML file.

Read more about GitHub Flavored Markdown.


Emojis can be added to Pull Requests, Issues, commit messages, repository descriptions, etc. using


The full list of supported Emojis on GitHub can be found at or scotch-io/All-Github-Emoji-Icons. A handy emoji search engine can be found at

The top 5 used Emojis on GitHub are:

  1. :shipit:
  2. :sparkles:
  3. :-1:
  4. :+1:
  5. :clap:


Images and GIFs can be added to comments, READMEs etc.:

![Alt Text](

Raw images from the repo can be used by calling them directly.:

![Alt Text]({user}/{repo}/raw/master/path/to/image.gif)

Peter don't care

All images are cached on GitHub, so if your host goes down, the image will remain available.

Embedding Images in GitHub Wiki

There are multiple ways of embedding images in Wiki pages. There's the standard Markdown syntax (shown above). But there's also a syntax that allows things like specifying the height or width of the image:

[[ | height = 100px ]]

Which produces:

Just a screenshot

Quick Quoting

When on a comment thread and you want to quote something someone previously said, highlight the text and press

, this will copy it into your text box in the block-quote format.

Quick Quote

Read more about quick quoting.

Pasting Clipboard Image to Comments

(Works on Chrome browsers only)

After taking a screenshot and adding it to the clipboard (mac:

), you can simply paste (
cmd-v / ctrl-v
) the image into the comment section and it will be auto-uploaded to github.

Pasting Clipboard Image to Comments

Read more about issue attachments.

Quick Licensing

When creating a repository, GitHub gives you the option of adding in a pre-made license:


You can also add them to existing repositories by creating a new file through the web interface. When the name

is typed in you will get an option to use a template:


Also works for


Read more about open source licensing.

Task Lists

In Issues and Pull requests check boxes can be added with the following syntax (notice the space):

- [ ] Be awesome
- [ ] Prepare dinner
  - [ ] Research recipe
  - [ ] Buy ingredients
  - [ ] Cook recipe
- [ ] Sleep

Task List

When they are clicked, they will be updated in the pure Markdown:

- [x] Be awesome
- [ ] Prepare dinner
  - [x] Research recipe
  - [x] Buy ingredients
  - [ ] Cook recipe
- [ ] Sleep

Read more about task lists.

Task Lists in Markdown Documents

In full Markdown documents read-only checklists can now be added using the following syntax:

- [ ] Mercury
- [x] Venus
- [x] Earth
  - [x] Moon
- [x] Mars
  - [ ] Deimos
  - [ ] Phobos
  • [ ] Mercury
  • [x] Venus
  • [x] Earth
    • [x] Moon
  • [x] Mars
    • [ ] Deimos
    • [ ] Phobos

Read more about task lists in markdown documents.

Relative Links

Relative links are recommended in your Markdown files when linking to internal content.

[Link to a header](#awesome-section)
[Link to a file](docs/readme)

Absolute links have to be updated whenever the URL changes (e.g., repository renamed, username changed, project forked). Using relative links makes your documentation easily stand on its own.

Read more about relative links.

Metadata and Plugin Support for GitHub Pages

Within Jekyll pages and posts, repository information is available within the

namespace, and can be displayed, for example, using
{{ site.github.project_title }}

The Jemoji and jekyll-mentions plugins enable emoji and @mentions in your Jekyll posts and pages to work just like you'd expect when interacting with a repository on

Read more about repository metadata and plugin support for GitHub Pages.

Viewing YAML Metadata in your Documents

Many blogging websites, like Jekyll with GitHub Pages, depend on some YAML-formatted metadata at the beginning of your post. GitHub will render this metadata as a horizontal table, for easier reading

YAML metadata

Read more about viewing YAML metadata in your documents.

Rendering Tabular Data

GitHub supports rendering tabular data in the form of

(comma-separated) and
(tab-separated) files.

Tabular data

Read more about rendering tabular data.

Rendering PDF

GitHub supports rendering PDF:


Read more about rendering PDF.

Revert a Pull Request

After a pull request is merged, you may find it does not help anything or it was a bad decision to merge the pull request.

You can revert it by clicking the Revert button on the right side of a commit in the pull request page to create a pull request with reverted changes to this specific pull request.

Revert button

Read more about reverting pull requests


Rendered Prose Diffs

Commits and pull requests, including rendered documents supported by GitHub (e.g., Markdown), feature source and rendered views.

Source / Rendered view

Click the "rendered" button to see the changes as they'll appear in the rendered document. Rendered prose view is handy when you're adding, removing, and editing text:

Rendered Prose Diffs

Read more about rendered prose diffs.

Diffable Maps

Any time you view a commit or pull request on GitHub that includes geodata, GitHub will render a visual representation of what was changed.

Diffable Maps

Read more about diffable maps.

Expanding Context in Diffs

Using the unfold button in the gutter of a diff, you can reveal additional lines of context with a click. You can keep clicking unfold until you've revealed the whole file, and the feature is available anywhere GitHub renders diffs.

Expanding Context in Diffs

Read more about expanding context in diffs.

Diff or Patch of Pull Request

You can get the diff of a Pull Request by adding a

extension to the end of the URL. For example:


extension would give you this in plain text:
diff --git a/ b/
index 88fcf69..8614873 100644
--- a/
+++ b/
@@ -28,6 +28,7 @@ All the hidden and not hidden features of Git and GitHub. This cheat sheet was i
 - [Merged Branches](#merged-branches)
 - [Quick Licensing](#quick-licensing)
 - [TODO Lists](#todo-lists)
+- [Relative Links](#relative-links)
 - [.gitconfig Recommendations](#gitconfig-recommendations)
     - [Aliases](#aliases)
     - [Auto-correct](#auto-correct)
@@ -381,6 +382,19 @@ When they are clicked, they will be updated in the pure Markdown:
 - [ ] Sleep


Rendering and diffing images

GitHub can display several common image formats, including PNG, JPG, GIF, and PSD. In addition, there are several ways to compare differences between versions of those image formats.

Diffable PSD

Read more about rendering and diffing images.


Hub is a command line Git wrapper that gives you extra features and commands that make working with GitHub easier.

This allows you to do things like:

$ hub clone tiimgreen/toc

Check out some more cool commands Hub has to offer.

Contribution Guidelines

GitHub supports adding 3 different files which help users contribute to your project. These files can either be placed in the root of your repository or a

directory under the root.


Adding a

file to either the root of your repository or a
directory will add a link to your file when a contributor creates an Issue or opens a Pull Request.

Contributing Guidelines

Read more about contributing guidelines.


You can define a template for all new issues opened in your project. The content of this file will pre-populate the new issue box when users create new issues. Add an

file to either the root of your repository or a

Read more about issue templates.

Issue template file generator

GitHub Issue template


You can define a template for all new pull requests opened in your project. The content of this file will pre-populate the text area when users create pull requests. Add a

file to either the root of your repository or a

Read more about pull request templates.

Pull request template file generator


GitHubs icons (Octicons) have now been open sourced.


Read more about GitHub's Octicons

GitHub Student Developer Pack

If you are a student you will be eligible for the GitHub Student Developer Pack. This gives you free credit, free trials and early access to software that will help you when developing.

GitHub Student Developer Pack

Read more about GitHub's Student Developer Pack

GitHub Resources

| Title | Link | | ----- | ---- | | GitHub Explore | | | GitHub Blog | | | GitHub Help | | | GitHub Training | | | GitHub Developer | | | Github Education (Free Micro Account and other stuff for students) | | | GitHub Best Practices | Best Practices List |

GitHub Talks

| Title | Link | | ----- | ---- | | How GitHub Uses GitHub to Build GitHub | | | Introduction to Git with Scott Chacon of GitHub | | | How GitHub No Longer Works | | | Git and GitHub Secrets | | | More Git and GitHub Secrets | |

SSH keys

You can get a list of public ssh keys in plain text format by visiting:{user}.keys


Read more about accessing public ssh keys.

Profile Image

You can get a user's profile image by visiting:{user}.png


Repository Templates

You can enable templating on your repository which allows anyone to copy the directory structure and files, allowing them to instantly use the files (e.g. for a tutorial or if writing boilerplate code). This can be enabled in the settings of your repository.


Changing to a template repository will give a new URL endpoint which can be shared and instantly allows users to use your repository as a template. Alternatively, they can go to your repository and click the 'Use as template' button.


Read more about using repositories as templates


Remove All Deleted Files from the Working Tree

When you delete a lot of files using

you can use the following command to remove them from the working tree and from the index, eliminating the need to remove each one individually:
$ git rm $(git ls-files -d)

For example:

$ git status
On branch master
Changes not staged for commit:
    deleted:    a
    deleted:    c

$ git rm $(git ls-files -d) rm 'a' rm 'c'

$ git status On branch master Changes to be committed: deleted: a deleted: c

Previous Branch

To move to the previous branch in Git:

$ git checkout -
# Switched to branch 'master'

$ git checkout -

Switched to branch 'next'

$ git checkout -

Switched to branch 'master'

Read more about Git branching.


Git Stripspace:

  • Strips trailing whitespace
  • Collapses newlines
  • Adds newline to end of file

A file must be passed when calling the command, e.g.:

$ git stripspace <

Read more about the Git


Checking out Pull Requests

Pull Requests are special branches on the GitHub repository which can be retrieved locally in several ways:

Retrieve a specific Pull Request and store it temporarily in

for quickly
-ing or
$ git fetch origin refs/pull/[PR-Number]/head

Acquire all Pull Request branches as local remote branches by refspec:

$ git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*'

Or setup the remote to fetch Pull Requests automatically by adding these corresponding lines in your repository's

[remote "origin"]
    fetch = +refs/heads/*:refs/remotes/origin/*
    url = [email protected]:tiimgreen/github-cheat-sheet.git
[remote "origin"]
    fetch = +refs/heads/*:refs/remotes/origin/*
    url = [email protected]:tiimgreen/github-cheat-sheet.git
    fetch = +refs/pull/*/head:refs/remotes/origin/pr/*

For Fork-based Pull Request contributions, it's useful to

a remote branch representing the Pull Request and create a local branch from it:
$ git checkout pr/42 pr-42

Or should you work on more repositories, you can globally configure fetching pull requests in the global git config instead.

git config --global --add remote.origin.fetch "+refs/pull/*/head:refs/remotes/origin/pr/*"

This way, you can use the following short commands in all your repositories:

git fetch origin
git checkout pr/42

Read more about checking out pull requests locally.

Empty Commits

Commits can be pushed with no code changes by adding

$ git commit -m "Big-ass commit" --allow-empty

Some use-cases for this (that make sense), include:

  • Annotating the start of a new bulk of work or a new feature.
  • Documenting when you make changes to the project that aren't code related.
  • Communicating with people using your repository.
  • The first commit of a repository:
    git commit -m "Initial commit" --allow-empty

Styled Git Status


$ git status


git status

By adding

$ git status -sb

this is produced:

git status -sb

Read more about the Git


Styled Git Log


$ git log --all --graph --pretty=format:'%Cred%h%Creset -%C(auto)%d%Creset %s %Cgreen(%cr) %C(bold blue)%Creset' --abbrev-commit --date=relative


git log --all --graph --pretty=format:'%Cred%h%Creset -%C(auto)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative

Credit to Palesz

This can be aliased using the instructions found here.

Read more about the Git


Git Query

A Git query allows you to search all your previous commit messages and find the most recent one matching the query.

$ git show :/query


(case-sensitive) is the term you want to search, this then finds the last one and gives details on the lines that were changed.
$ git show :/typo

git show :/query


to quit.

Git Grep

Git Grep will return a list of lines matching a pattern.


$ git grep aliases
will show all the files containing the string aliases.

git grep aliases


to quit.

You can also use multiple flags for more advanced search. For example:

  • -e
    The next parameter is the pattern (e.g., regex)
  • --and
    Combine multiple patterns.

Use it like this:

 $ git grep -e pattern --and -e anotherpattern

Read more about the Git


Merged Branches


$ git branch --merged

will give you a list of all branches that have been merged into your current branch.


$ git branch --no-merged

will give you a list of branches that have not been merged into your current branch.

Read more about the Git


Fixup and Autosquash

If there is something wrong with a previous commit (can be one or more from HEAD), for example

, run the following command after you've amended the problem:
$ git commit --fixup=abcde
$ git rebase abcde^ --autosquash -i
Read more about the Git
Read more about the Git

Web Server for Browsing Local Repositories

Use the Git

command to instantly browse your working repository in
. This command is a simple script to set up
and a web server for browsing the local repository.
$ git instaweb


Git instaweb

Read more about the Git


Git Configurations


file contains all your Git configurations.


Aliases are helpers that let you define your own git calls. For example you could set

git a
to run
git add --all

To add an alias, either navigate to

and fill it out in the following format:
  co = checkout
  cm = commit
  p = push
  # Show verbose output about tags, branches or remotes
  tags = tag -l
  branches = branch -a
  remotes = remote -v

...or type in the command-line:

$ git config --global alias.new_alias git_function

For example:

$ git config --global commit

For an alias with multiple functions use quotes:

$ git config --global 'add -A . && commit'

Some useful aliases include:

| Alias | Command | What to Type | | --- | --- | --- | |

git cm
git commit
git config --global commit
| |
git co
git checkout
git config --global checkout
| |
git ac
git add . -A
git commit
git config --global '!git add -A && git commit'
| |
git st
git status -sb
git config --global 'status -sb'
| |
git tags
git tag -l
git config --global alias.tags 'tag -l'
| |
git branches
git branch -a
git config --global alias.branches 'branch -a'
| |
git cleanup
git branch --merged \| grep -v '*' \| xargs git branch -d
git config --global alias.cleanup "!git branch --merged \| grep -v '*' \| xargs git branch -d"
| |
git remotes
git remote -v
git config --global alias.remotes 'remote -v'
| |
git lg
git log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)%Creset' --abbrev-commit --
git config --global alias.lg "log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)%Creset' --abbrev-commit --"

Some Aliases are taken from @mathiasbynens dotfiles:


Git gives suggestions for misspelled commands and if auto-correct is enabled the command can be fixed and executed automatically. Auto-correct is enabled by specifying an integer which is the delay in tenths of a second before git will run the corrected command. Zero is the default value where no correcting will take place, and a negative value will run the corrected command with no delay.

For example, if you type

git comit
you will get this:
$ git comit -m "Message"
# git: 'comit' is not a git command. See 'git --help'.

Did you mean this?


Auto-correct can be enabled like this (with a 1.5 second delay):

$ git config --global help.autocorrect 15

So now the command

git comit
will be auto-corrected to
git commit
like this:
$ git comit -m "Message"
# WARNING: You called a Git command named 'comit', which does not exist.
# Continuing under the assumption that you meant 'commit'
# in 1.5 seconds automatically...

The delay before git will rerun the command is so the user has time to abort.


To add more color to your Git output:

$ git config --global color.ui 1

Read more about the Git


Git Resources

| Title | Link | | ----- | ---- | | Official Git Site | | | Official Git Video Tutorials | | | Code School Try Git | | | Introductory Reference & Tutorial for Git | | | Official Git Tutorial | | | Everyday Git | | | Git Immersion | | | Git God | | | Git for Computer Scientists | | | Git Magic | | | Git Visualization Playground | | | Learn Git Branching | | | A collection of useful .gitignore templates | | | Unixorn's git-extra-commands collection of git scripts | |

Git Books

| Title | Link | | ----- | ---- | | Pragmatic Version Control Using Git | | | Pro Git | | | Git Internals PluralSight | | | Git in the Trenches | | | Version Control with Git | | | Pragmatic Guide to Git | | | Git: Version Control for Everyone | |

Git Videos

| Title | Link | | ----- | ---- | | Linus Torvalds on Git | | | Introduction to Git with Scott Chacon | | | Git From the Bits Up | | | Graphs, Hashes, and Compression, Oh My! | | | GitHub Training & Guides | |

Git Articles

| Title | Link | | ----- | ---- | | GitHub Flow | | | Migrating to Git Large File Storate (Git LFS) | |

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.