git + hub = github

hub is a command line tool that wraps git in order to extend it with extra features and commands that make working with GitHub easier.

$ hub clone rtomayko/tilt

# expands to:
$ git clone git://

hub is best aliased as git, so you can type $ git <command> in the shell and get all the usual hub features. See "Aliasing" below.



  • git 1.7.3 or newer
  • Ruby 1.8.6 or newer


Installing on OS X is easiest with Homebrew:

$ brew install hub


hub is easily installed as a standalone script:

$ curl -sLo ~/bin/hub &&
  chmod +x ~/bin/hub

Assuming "~/bin/" is in your $PATH, you're ready to roll:

$ hub version
git version 1.7.6
hub version 1.8.3

On Windows

If you have mysysgit, open "Git Bash" and follow the steps above but put the hub executable in /bin instead of ~/bin.

Avoid aliasing hub as git due to the fact that mysysgit automatically configures your prompt to include git information, and you want to avoid slowing that down. See Is your shell prompt slow?


Though not recommended, hub can also be installed as a RubyGem:

$ gem install hub

(It's not recommended for casual use because of the RubyGems startup time. See this gist for information.)

Standalone via RubyGems

$ gem install hub
$ hub hub standalone > ~/bin/hub && chmod +x ~/bin/hub

This installs a standalone version which doesn't require RubyGems to run, so it's faster.


You can also install from source:

$ git clone git://
$ cd hub
$ rake install prefix=/usr/local

Help! It's slow!

Is hub noticeably slower than plain git?

That is inconvenient, especially if you want to alias hub as git. Few things you can try:

  • Find out which ruby is used for the hub executable:

    head -1 `which hub`
  • That ruby should be speedy. Time it with:

    time /usr/bin/ruby -e0
    #=> it should be below 0.01 s total
  • Check that Ruby isn't loading something shady:

    echo $RUBYOPT
  • Check your GC settings

General recommendation: you should change hub's shebang line to run with system ruby (usually /usr/bin/ruby) instead of currently active ruby (/usr/bin/env ruby). Also, Ruby 1.8 is speedier than 1.9.

Is your shell prompt slow?

Does your prompt show git information? Hub may be slowing down your prompt.

This can happen if you've aliased hub as git. This is fine when you use git manually, but may be unacceptable for your prompt, which doesn't need hub features anyway!

The solution is to identify which shell functions are calling git, and replace each occurrence of that with command git. This is a shell feature that enables you to call a command directly and skip aliases and functions wrapping it.


Using hub feels best when it's aliased as git. This is not dangerous; your normal git commands will all work. hub merely adds some sugar.

hub alias displays instructions for the current shell. With the -s flag, it outputs a script suitable for eval.

You should place this command in your .bash_profile or other startup script:

eval "$(hub alias -s)"

Shell tab-completion

hub repository contains tab-completion scripts for bash and zsh. These scripts complement existing completion scripts that ship with git.


Assuming you've aliased hub as git, the following commands now have superpowers:

git clone

$ git clone schacon/ticgit
> git clone git://

$ git clone -p schacon/ticgit
> git clone [email protected]:schacon/ticgit.git

$ git clone resque
> git clone [email protected]/YOUR_USER/resque.git

git remote add

$ git remote add rtomayko
> git remote add rtomayko git://

$ git remote add -p rtomayko
> git remote add rtomayko [email protected]:rtomayko/CURRENT_REPO.git

$ git remote add origin
> git remote add origin git://

git fetch

$ git fetch mislav
> git remote add mislav git://
> git fetch mislav

$ git fetch mislav,xoebus
> git remote add mislav ...
> git remote add xoebus ...
> git fetch --multiple mislav xoebus

git cherry-pick

$ git cherry-pick
> git remote add -f mislav git://
> git cherry-pick SHA

$ git cherry-pick mislav@SHA
> git remote add -f mislav git://
> git cherry-pick SHA

$ git cherry-pick mislav@SHA
> git fetch mislav
> git cherry-pick SHA

git am, git apply

$ git am
> curl -o /tmp/55.patch
> git am /tmp/55.patch

$ git am --ignore-whitespace
> curl -o /tmp/fdb9921.patch
> git am --ignore-whitespace /tmp/fdb9921.patch

$ git apply
> curl -o /tmp/gist-8da7fb575debd88c54cf.txt
> git apply /tmp/gist-8da7fb575debd88c54cf.txt

git fork

$ git fork
[ repo forked on GitHub ]
> git remote add -f YOUR_USER [email protected]:YOUR_USER/CURRENT_REPO.git

git pull-request

# while on a topic branch called "feature":
$ git pull-request
[ opens text editor to edit title & body for the request ]
[ opened pull request on GitHub for "YOUR_USER:feature" ]

# explicit title, pull base & head:
$ git pull-request "I've implemented feature X" -b defunkt:master -h mislav:feature

$ git pull-request -i 123
[ attached pull request to issue #123 ]

git checkout

$ git checkout
> git remote add -f -t feature git://github:com/mislav/hub.git
> git checkout --track -B mislav-feature mislav/feature

$ git checkout custom-branch-name

git merge

$ git merge
> git fetch git:// +refs/heads/feature:refs/remotes/mislav/feature
> git merge mislav/feature --no-ff -m 'Merge pull request #73 from mislav/feature...'

git create

$ git create
[ repo created on GitHub ]
> git remote add origin [email protected]:YOUR_USER/CURRENT_REPO.git

# with description:
$ git create -d 'It shall be mine, all mine!'

$ git create recipes
[ repo created on GitHub ]
> git remote add origin [email protected]:YOUR_USER/recipes.git

$ git create sinatra/recipes
[ repo created in GitHub organization ]
> git remote add origin [email protected]:sinatra/recipes.git

git init

$ git init -g
> git init
> git remote add origin [email protected]:YOUR_USER/REPO.git

git push

$ git push origin,staging,qa bert_timeout
> git push origin bert_timeout
> git push staging bert_timeout
> git push qa bert_timeout

git browse

$ git browse
> open

$ git browse -- commit/SHA
> open

$ git browse -- issues
> open

$ git browse schacon/ticgit
> open

$ git browse schacon/ticgit commit/SHA
> open

$ git browse resque
> open

$ git browse resque network
> open

git compare

$ git compare refactor
> open

$ git compare 1.0..1.1
> open

$ git compare -u fix
> (

$ git compare other-user patch
> open

git submodule

$ hub submodule add wycats/bundler vendor/bundler
> git submodule add git:// vendor/bundler

$ hub submodule add -p wycats/bundler vendor/bundler
> git submodule add [email protected]:wycats/bundler.git vendor/bundler

$ hub submodule add -b ryppl --name pip ryppl/pip vendor/pip
> git submodule add -b ryppl --name pip git:// vendor/pip

git help

$ git help
> (improved git help)
$ git help hub
> (hub man page)


GitHub OAuth authentication

Hub will prompt for GitHub username & password the first time it needs to access the API and exchange it for an OAuth token, which it saves in "~/.config/hub".

HTTPS instead of git protocol

If you prefer using the HTTPS protocol for GitHub repositories instead of the git protocol for read and ssh for write, you can set "hub.protocol" to "https".

# default behavior
$ git clone defunkt/repl
< git clone >

# opt into HTTPS:
$ git config --global hub.protocol https
$ git clone defunkt/repl
< https clone >


These instructions assume that you already have hub installed and aliased as git (see "Aliasing").

  1. Clone hub:
    git clone defunkt/hub && cd hub
  2. Ensure Bundler is installed:
    which bundle || gem install bundler
  3. Install development dependencies:
    bundle install
  4. Verify that existing tests pass:
    bundle exec rake
  5. Create a topic branch:
    git checkout -b feature
  6. Make your changes. (It helps a lot if you write tests first.)
  7. Verify that tests still pass:
    bundle exec rake
  8. Fork hub on GitHub (adds a remote named "YOUR_USER"):
    git fork
  9. Push to your fork:
    git push -u YOUR_USER feature
  10. Open a pull request describing your changes:
    git pull-request


Prior art

These projects also aim to either improve git or make interacting with GitHub simpler: