hub(1) – git + hub = github
## SYNOPSIS
`hub` [`–noop`] <COMMAND> <OPTIONS>
`hub alias` [`-s`] [<SHELL>]
### Expanded git commands:
`git init -g` <OPTIONS>
`git clone` [`-p`] <OPTIONS> [<USER>/]<REPOSITORY> <DIRECTORY>
`git remote add` [`-p`] <OPTIONS> <“>USER>
`git fetch` <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”.
To avoid being prompted, use <GITHUB_USER> and <GITHUB_PASSWORD> environment variables.
If you prefer the HTTPS protocol for GitHub repositories, you can set “hub.protocol” to “https”. This will affect `clone`, `fork`, `remote add` and other operations that expand references to GitHub repositories as full URLs that otherwise use git and ssh protocols.
$ git config --global hub.protocol https
### GitHub Enterprise
By default, hub will only work with repositories that have remotes which point to github.com. GitHub Enterprise hosts need to be whitelisted to configure hub to treat such remotes same as github.com:
$ git config --global --add hub.host my.git.org
The default host for commands like `init` and `clone` is still github.com, but this can be affected with the <GITHUB_HOST> environment variable:
$ GITHUB_HOST=my.git.org git clone myproject
## EXAMPLES
{{README}}
## BUGS
<github.com/github/hub/issues>
## AUTHORS
<github.com/github/hub/contributors>
## SEE ALSO
git(1), git-clone(1), git-remote(1), git-init(1), <github.com>, <github.com/github/hub>