HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mislav
hub
Go2009–2022
mislav / hub

hub

A command-line tool that makes git easier to use with GitHub.

64Distinct people
71Mentions
0Explicit recommenders
23KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A command-line tool that makes git easier to use with GitHub.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

  • cli/cli · linked in 2 of the same discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 8:27:21 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year71 dated mentions

Observed mentions: 2009-12-09 05:56:17 UTC to 2022-06-05 16:57:38 UTC.

0510152009-01-01 00:00:00 UTC to 2010-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20092010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 8 mentions; 3 submissions, 5 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 17 mentions; 4 submissions, 13 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20092009-01-01 00:00:00 UTC2010-01-01 00:00:00 UTC110
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC101
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC110
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC808
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC725
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC835
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC17413
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC716
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC514
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC303
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC808
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
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. For an official, potentially more user-friendly command-line interface to GitHub, see cli.github.com and this comparison. This repository and its issue tracker is not for reporting problems with GitHub.com web interface. If you have a problem with GitHub itself, please contact Support. Usage $ hub clone rtomayko/tilt #=> git clone https://github.com/rtomayko/tilt.git # or, if you prefer the SSH protocol: $ git config --global hub.protocol ssh $ hub clone rtomayko/tilt #=> git clone git@github.com:rtomayko/tilt.git See usage examples or the full reference documentation to see all available commands and flags. hub can also be used to make shell scripts that directly interact with the GitHub API. hub can be safely aliased as git, so you can type $ git <command> in the shell and have it expanded with hub features. Installation The hub executable has no dependencies, but since it was designed to wrap git, it's recommended to have at least git 1.7.3 or newer. platform manager command to run macOS, Linux Homebrew brew install hub macOS, Linux Nix nix-env -i hub Windows Scoop scoop install hub Windows Chocolatey choco install hub Fedora Linux DNF sudo dnf install hub Arch Linux pacman sudo pacman -S hub FreeBSD pkg(8) pkg install hub Debian, Ubuntu apt(8) sudo apt install hub Ubuntu Snap We do not recommend installing the snap anymore. openSUSE Zypper sudo zypper install hub Void Linux xbps sudo xbps-install -S hub Gentoo Portage sudo emerge dev-vcs/hub any conda conda install -c conda-forge hub Packages other than Homebrew are community-maintained (thank you!) and they are not guaranteed to match the latest hub release. Check hub version after installing a community package. Standalone hub can be easily installed as an executable. Download the latest binary for your system and put it anywhere in your executable path. GitHub Actions hub is ready to be used in your GitHub Actions workflows: steps: - uses: actions/checkout@v2 - name: List open pull requests run: hub pr list env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} Note that the default secrets.GITHUB_TOKEN will only work for API operations scoped to the repository that runs this workflow. If you need to interact with other repositories, generate a Personal Access Token with at least the repo scope and add it to your repository secrets. Source Prerequisites for building from source are: make Go 1.11+ Clone this repository and run make install: git clone \ --config transfer.fsckobjects=false \ --config receive.fsckobjects=false \ --config fetch.fsckobjects=false \ https://github.com/github/hub.git cd hub make install prefix=/usr/local Aliasing Some hub features feel 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)" PowerShell If you're using PowerShell, you can set an alias for hub by placing the following in your PowerShell profile (usually ~/Documents/WindowsPowerShell/Microsoft.PowerShell_profile.ps1): Set-Alias git hub A simple way to do this is to run the following from the PowerShell prompt: Add-Content $PROFILE "`nSet-Alias git hub" Note: You'll need to restart your PowerShell console in order for the changes to be picked up. If your PowerShell profile doesn't exist, you can create it by running the following: New-Item -Type file -Force $PROFILE Shell tab-completion hub repository contains tab-completion scripts for bash, zsh and fish. These scripts complement existing completion scripts that ship with git. Meta Bugs: https://github.com/github/hub/issues Authors: https://github.com/github/hub/contributors Our Code of Conduct
Read the full README on GitHub

What Hacker News says

5 sources
Yeah, I realize a lot of devs have already have their own setups that work extremely well for them. Unfortunately anytime you transition to a new tool you're obviously going to break _someone's_ workflow. That said, switching to something like GitHub doesn't necessarily mean developers all _have_ to use exactly the same workflow. For example, if you're more comfortable in the command line, there are tools like [hub][1] and [git-gitlab][2] available which let you perform common tasks in GitHub/GitLab using the CLI. I just think that long-term it's better to have a good baseline user experience that devs can then extend with their own personal tools if they choose than to have a not-so-great one that _requires_ you to extend it with your own tools before it's anywhere near as good as what a well-designed Web UI provides out-of-the-box; even
Read the rest
if in the short-term that means breaking some dev's workflows. Obviously that doesn't mean you shouldn't try to maintain compatibility with developer's existing workflows wherever possible though. For example, GitLab and GitHub both let you reply to issues by email, and RocketChat has an IRC plugin that lets you connect RocketChat rooms to an IRC channel. [1]: https://github.com/github/hub [2]: https://github.com/numa08/git-gitlab
In Maintainers Don't Scale

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.