GitHub doesn't support ranges with two dots, only three. With these two being equivalent in case of linear history, it's generally safe to convert the range pasted on the command-line to three dots. This is to avoid confusion where GitHub would display a 404 page otherwise. See "specifying ranges" in the `git-rev-parse` man page. closes #80
Changes: - `browse` and `compare` always open HTTPS - the `-p` flag for these commands has no effect anymore - updated `browse` URL for wiki pages - cherry-picking a URL doesn't add a new remote as private
Creates new remotes if needed and fetches objects before cherry-picking. $ git cherry-pick http://github.com/mislav/REPO/commit/SHA > git remote add -f mislav git://github.com/mislav/REPO.git > git cherry-pick SHA
A remote must be an existing repo on GitHub. $ git fetch mislav > git remote add mislav git://github.com/mislav/REPO.git > git fetch mislav
…ub" gem If users keep the gem installed, they have a chance to be notified of updates and they can refresh their standalone script. Also, executables in ~/bin should have precedence over gem executables, so no need to uninstall.
…epo issues`) New abilities: $ hub compare -> When on a branch that tracks "remotebranch", for example, this opens "github.com/user/repo/compare/remotebranch". In effect if the tracked branch is not "master". $ hub browse reque issues -> open http://github.com/user/resque/issues $ hub browse -> When on a branch that tracks "remotebranch", for example, this opens "github.com/user/repo/tree/remotebranch". In effect if the tracked branch is not "master". $ hub browse -- commits -> open http://github.com/user/repo/commits/master If this branch is tracking a remote branch: -> open http://github.com/user/repo/commits/remotebranch Supported subpages: - "tree" (default) - "wiki" - "commits" - "issues", "network", "downloads" or any other arbitrary string is simply appended to URL path