github.com/jingweno/gh@v2.1.1-0.20221007190738-04a7985fa9a1+incompatible/man/gh.1 (about) 1 .\" generated with Ronn/v0.7.3 2 .\" http://github.com/rtomayko/ronn/tree/0.7.3 3 . 4 .TH "GH" "1" "January 2014" "GITHUB" "gh Manual" 5 . 6 .SH "NAME" 7 \fBgh\fR \- gh + h = github 8 . 9 .SH "SYNOPSIS" 10 \fBgh\fR [\fB\-\-noop\fR] \fICOMMAND\fR \fIOPTIONS\fR 11 . 12 .br 13 \fBgh alias\fR [\fB\-s\fR] [\fISHELL\fR] 14 . 15 .SS "Expanded git commands:" 16 \fBgit init \-g\fR \fIOPTIONS\fR 17 . 18 .br 19 \fBgit clone\fR [\fB\-p\fR] \fIOPTIONS\fR [\fIUSER\fR/]\fIREPOSITORY\fR \fIDIRECTORY\fR 20 . 21 .br 22 \fBgit remote add\fR [\fB\-p\fR] \fIOPTIONS\fR \fIUSER\fR[/\fIREPOSITORY\fR] 23 . 24 .br 25 \fBgit remote set\-url\fR [\fB\-p\fR] \fIOPTIONS\fR \fIREMOTE\-NAME\fR \fIUSER\fR[/\fIREPOSITORY\fR] 26 . 27 .br 28 \fBgit fetch\fR \fIUSER\-1\fR,[\fIUSER\-2\fR,\.\.\.] 29 . 30 .br 31 \fBgit checkout\fR \fIPULLREQ\-URL\fR [\fIBRANCH\fR] 32 . 33 .br 34 \fBgit merge\fR \fIPULLREQ\-URL\fR 35 . 36 .br 37 \fBgit cherry\-pick\fR \fIGITHUB\-REF\fR 38 . 39 .br 40 \fBgit am\fR \fIGITHUB\-URL\fR 41 . 42 .br 43 \fBgit apply\fR \fIGITHUB\-URL\fR 44 . 45 .br 46 \fBgit push\fR \fIREMOTE\-1\fR,\fIREMOTE\-2\fR,\.\.\.,\fIREMOTE\-N\fR [\fIREF\fR] 47 . 48 .br 49 \fBgit submodule add\fR [\fB\-p\fR] \fIOPTIONS\fR [\fIUSER\fR/]\fIREPOSITORY\fR \fIDIRECTORY\fR 50 . 51 .SS "Custom git commands:" 52 \fBgit create\fR [\fINAME\fR] [\fB\-p\fR] [\fB\-d\fR \fIDESCRIPTION\fR] [\fB\-h\fR \fIHOMEPAGE\fR] 53 . 54 .br 55 \fBgit browse\fR [\fB\-u\fR] [[\fIUSER\fR\fB/\fR]\fIREPOSITORY\fR] [SUBPAGE] 56 . 57 .br 58 \fBgit compare\fR [\fB\-u\fR] [\fIUSER\fR] [[\fISTART\fR\.\.\.]\fIEND\fR] 59 . 60 .br 61 \fBgit fork\fR [\fB\-\-no\-remote\fR] 62 . 63 .br 64 \fBgit pull\-request\fR [\fB\-f\fR] [\fB\-m\fR \fIMESSAGE\fR|\fB\-F\fR \fIFILE\fR|\fB\-i\fR \fIISSUE\fR|\fIISSUE\-URL\fR] [\fB\-b\fR \fIBASE\fR] [\fB\-h\fR \fIHEAD\fR] 65 . 66 .br 67 \fBgit release create\fR [\fB\-d\fR] [\fB\-p\fR] [\fB\-a\fR \fIASSETS\-DIR\fR] [\fB\-m\fR \fIMESSAGE\fR|\fB\-f\fR \fIFILE\fR] \fITAG\fR \fBgit issue create\fR [\fB\-m\fR \fIMESSAGE\fR|\fB\-f\fR \fIFILE\fR] [\fB\-l\fR \fILABEL\-1\fR,\fILABEL\-2\fR,\.\.\.,\fILABEL\-N\fR] \fBgit ci\-status\fR [\fB\-v\fR] [\fICOMMIT\fR] 68 . 69 .SH "DESCRIPTION" 70 gh enhances various git commands to ease most common workflows with GitHub\. 71 . 72 .TP 73 \fBgh \-\-noop\fR \fICOMMAND\fR 74 Shows which command(s) would be run as a result of the current command\. Doesn\'t perform anything\. 75 . 76 .TP 77 \fBgh alias\fR [\fB\-s\fR] [\fISHELL\fR] 78 Shows shell instructions for wrapping git\. If given, \fISHELL\fR specifies the type of shell; otherwise defaults to the value of SHELL environment variable\. With \fB\-s\fR, outputs shell script suitable for \fBeval\fR\. 79 . 80 .TP 81 \fBgit init\fR \fB\-g\fR \fIOPTIONS\fR 82 Create a git repository as with git\-init(1) and add remote \fBorigin\fR at "git@github\.com:\fIUSER\fR/\fIREPOSITORY\fR\.git"; \fIUSER\fR is your GitHub username and \fIREPOSITORY\fR is the current working directory\'s basename\. 83 . 84 .TP 85 \fBgit clone\fR [\fB\-p\fR] \fIOPTIONS\fR [\fIUSER\fR\fB/\fR]\fIREPOSITORY\fR \fIDIRECTORY\fR 86 Clone repository "git://github\.com/\fIUSER\fR/\fIREPOSITORY\fR\.git" into \fIDIRECTORY\fR as with git\-clone(1)\. When \fIUSER\fR/ is omitted, assumes your GitHub login\. 87 . 88 .IP 89 If the repository is private or the current user has push access to the repository, gh will use the ssh protocol for cloning\. Use \fB\-p\fR to select the ssh protocol unconditionally\. HTTPS protocol can be used instead by setting "gh\.protocol" (see \fICONFIGURATION\fR)\. 90 . 91 .TP 92 \fBgit remote add\fR [\fB\-p\fR] \fIOPTIONS\fR \fIUSER\fR[\fB/\fR\fIREPOSITORY\fR] 93 Add remote "git://github\.com/\fIUSER\fR/\fIREPOSITORY\fR\.git" as with git\-remote(1)\. When /\fIREPOSITORY\fR is omitted, the basename of the current working directory is used\. With \fB\-p\fR, use private remote "git@github\.com:\fIUSER\fR/\fIREPOSITORY\fR\.git"\. If \fIUSER\fR is "origin" then uses your GitHub login\. 94 . 95 .TP 96 \fBgit remote set\-url\fR [\fB\-p\fR] \fIOPTIONS\fR \fIREMOTE\-NAME\fR \fIUSER\fR[/\fIREPOSITORY\fR] 97 Sets the url of remote \fIREMOTE\-NAME\fR using the same rules as \fBgit remote add\fR\. 98 . 99 .TP 100 \fBgit fetch\fR \fIUSER\-1\fR,[\fIUSER\-2\fR,\.\.\.] 101 Adds missing remote(s) with \fBgit remote add\fR prior to fetching\. New remotes are only added if they correspond to valid forks on GitHub\. 102 . 103 .TP 104 \fBgit checkout\fR \fIPULLREQ\-URL\fR [\fIBRANCH\fR] 105 Checks out the head of the pull request as a local branch, to allow for reviewing, rebasing and otherwise cleaning up the commits in the pull request before merging\. The name of the local branch can explicitly be set with \fIBRANCH\fR\. 106 . 107 .TP 108 \fBgit merge\fR \fIPULLREQ\-URL\fR 109 Merge the pull request with a commit message that includes the pull request ID and title, similar to the GitHub Merge Button\. 110 . 111 .TP 112 \fBgit cherry\-pick\fR \fIGITHUB\-REF\fR 113 Cherry\-pick a commit from a fork using either full URL to the commit or GitHub\-flavored Markdown notation, which is \fBuser@sha\fR\. If the remote doesn\'t yet exist, it will be added\. A \fBgit fetch <user>\fR is issued prior to the cherry\-pick attempt\. 114 . 115 .TP 116 \fBgit [am|apply]\fR \fIGITHUB\-URL\fR 117 Downloads the patch file for the pull request or commit at the URL and applies that patch from disk with \fBgit am\fR or \fBgit apply\fR\. Similar to \fBcherry\-pick\fR, but doesn\'t add new remotes\. \fBgit am\fR creates commits while preserving authorship info while \fBapply\fR only applies the patch to the working copy\. 118 . 119 .TP 120 \fBgit push\fR \fIREMOTE\-1\fR,\fIREMOTE\-2\fR,\.\.\.,\fIREMOTE\-N\fR [\fIREF\fR] 121 Push \fIREF\fR to each of \fIREMOTE\-1\fR through \fIREMOTE\-N\fR by executing multiple \fBgit push\fR commands\. 122 . 123 .TP 124 \fBgit submodule add\fR [\fB\-p\fR] \fIOPTIONS\fR [\fIUSER\fR/]\fIREPOSITORY\fR \fIDIRECTORY\fR 125 Submodule repository "git://github\.com/\fIUSER\fR/\fIREPOSITORY\fR\.git" into \fIDIRECTORY\fR as with git\-submodule(1)\. When \fIUSER\fR/ is omitted, assumes your GitHub login\. With \fB\-p\fR, use private remote "git@github\.com:\fIUSER\fR/\fIREPOSITORY\fR\.git"\. 126 . 127 .TP 128 \fBgit help\fR 129 Display enhanced git\-help(1)\. 130 . 131 .P 132 gh also adds some custom commands that are otherwise not present in git: 133 . 134 .TP 135 \fBgit create\fR [\fINAME\fR] [\fB\-p\fR] [\fB\-d\fR \fIDESCRIPTION\fR] [\fB\-h\fR \fIHOMEPAGE\fR] 136 Create a new public GitHub repository from the current git repository and add remote \fBorigin\fR at "git@github\.com:\fIUSER\fR/\fIREPOSITORY\fR\.git"; \fIUSER\fR is your GitHub username and \fIREPOSITORY\fR is the current working directory name\. To explicitly name the new repository, pass in \fINAME\fR, optionally in \fIORGANIZATION\fR/\fINAME\fR form to create under an organization you\'re a member of\. With \fB\-p\fR, create a private repository, and with \fB\-d\fR and \fB\-h\fR set the repository\'s description and homepage URL, respectively\. 137 . 138 .TP 139 \fBgit browse\fR [\fB\-u\fR] [[\fIUSER\fR\fB/\fR]\fIREPOSITORY\fR] [SUBPAGE] 140 Open repository\'s GitHub page in the system\'s default web browser using \fBopen(1)\fR or the \fBBROWSER\fR env variable\. If the repository isn\'t specified, \fBbrowse\fR opens the page of the repository found in the current directory\. If SUBPAGE is specified, the browser will open on the specified subpage: one of "wiki", "commits", "issues" or other (the default is "tree")\. With \fB\-u\fR, outputs the URL rather than opening the browser\. 141 . 142 .TP 143 \fBgit compare\fR [\fB\-u\fR] [\fIUSER\fR] [[\fISTART\fR\.\.\.]\fIEND\fR] 144 Open a GitHub compare view page in the system\'s default web browser\. \fISTART\fR to \fIEND\fR are branch names, tag names, or commit SHA1s specifying the range of history to compare\. If a range with two dots (\fBa\.\.b\fR) is given, it will be transformed into one with three dots\. If \fISTART\fR is omitted, GitHub will compare against the base branch (the default is "master")\. If \fIEND\fR is omitted, GitHub compare view is opened for the current branch\. With \fB\-u\fR, outputs the URL rather than opening the browser\. 145 . 146 .TP 147 \fBgit fork\fR [\fB\-\-no\-remote\fR] 148 Forks the original project (referenced by "origin" remote) on GitHub and adds a new remote for it under your username\. 149 . 150 .TP 151 \fBgit pull\-request\fR [\fB\-f\fR] [\fB\-m\fR \fIMESSAGE\fR|\fB\-F\fR \fIFILE\fR|\fB\-i\fR \fIISSUE\fR|\fIISSUE\-URL\fR] [\fB\-b\fR \fIBASE\fR] [\fB\-h\fR \fIHEAD\fR] 152 Opens a pull request on GitHub for the project that the "origin" remote points to\. The default head of the pull request is the current branch\. Both base and head of the pull request can be explicitly given in one of the following formats: "branch", "owner:branch", "owner/repo:branch"\. This command will abort operation if it detects that the current topic branch has local commits that are not yet pushed to its upstream branch on the remote\. To skip this check, use \fB\-f\fR\. 153 . 154 .IP 155 Without \fIMESSAGE\fR or \fIFILE\fR, a text editor will open in which title and body of the pull request can be entered in the same manner as git commit message\. Pull request message can also be passed via stdin with \fB\-F \-\fR\. 156 . 157 .IP 158 Issue to pull request conversion via \fB\-i <ISSUE>\fR or \fIISSUE\-URL\fR arguments is deprecated and will likely be removed from the future versions of both hub and GitHub API\. 159 . 160 .TP 161 \fBgit release\fR 162 Retrieves releases from GitHub for the project that the "origin" remote points to\. 163 . 164 .TP 165 \fBgit release create\fR [\fB\-d\fR] [\fB\-p\fR] [\fB\-a\fR \fIASSETS\-DIR\fR] [\fB\-m\fR \fIMESSAGE\fR|\fB\-f\fR \fIFILE\fR] \fITAG\fR 166 Creates a new release in GitHub for the project that the "origin" remote points to\. It requires the name of the tag to release as a first argument\. 167 . 168 .IP 169 Specify the assets to include in the release from a directory via \fB\-a\fR\. Without \fB\-a\fR, it finds assets from "releases/TAG" of the current directory\. 170 . 171 .IP 172 Without \fIMESSAGE\fR or \fIFILE\fR, a text editor will open in which title and body of the release can be entered in the same manner as git commit message\. 173 . 174 .IP 175 If \fB\-d\fR is given, it creates a draft release\. 176 . 177 .IP 178 If \fB\-p\fR is given, it creates a pre\-release\. 179 . 180 .TP 181 \fBgit issue\fR 182 List summary of the open issues for the project that the "origin" remote points to\. 183 . 184 .TP 185 \fBgit issue create\fR [\fB\-m\fR \fIMESSAGE\fR|\fB\-f\fR \fIFILE\fR] [\fB\-l\fR \fILABEL\-1\fR,\fILABEL\-2\fR,\.\.\.,\fILABEL\-N\fR] 186 Creates an issue for the project that the "origin" remote points to\. 187 . 188 .IP 189 Without \fIMESSAGE\fR or \fIFILE\fR, a text editor will open in which title and body of the release can be entered in the same manner as git commit message\. 190 . 191 .IP 192 Specify one or more labels via \fB\-a\fR\. 193 . 194 .TP 195 \fBgit ci\-status\fR [\fB\-v\fR] [\fICOMMIT\fR] 196 Looks up the SHA for \fICOMMIT\fR in GitHub Status API and displays the latest status\. Exits with one of: 197 . 198 .br 199 success (0), error (1), failure (1), pending (2), no status (3) 200 . 201 .IP 202 If \fB\-v\fR is given, additionally print the URL to CI build results\. 203 . 204 .SH "CONFIGURATION" 205 gh 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/gh"\. 206 . 207 .P 208 To avoid being prompted, use \fIGITHUB_USER\fR and \fIGITHUB_PASSWORD\fR environment variables\. 209 . 210 .P 211 If you prefer the HTTPS protocol for GitHub repositories, you can set "gh\.protocol" to "https"\. This will affect \fBclone\fR, \fBfork\fR, \fBremote add\fR and other operations that expand references to GitHub repositories as full URLs that otherwise use git and ssh protocols\. 212 . 213 .IP "" 4 214 . 215 .nf 216 217 $ git config \-\-global gh\.protocol https 218 . 219 .fi 220 . 221 .IP "" 0 222 . 223 .SS "GitHub Enterprise" 224 By default, gh 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: 225 . 226 .IP "" 4 227 . 228 .nf 229 230 $ git config \-\-global \-\-add gh\.host my\.git\.org 231 . 232 .fi 233 . 234 .IP "" 0 235 . 236 .P 237 The default host for commands like \fBinit\fR and \fBclone\fR is still github\.com, but this can be affected with the \fIGITHUB_HOST\fR environment variable: 238 . 239 .IP "" 4 240 . 241 .nf 242 243 $ GITHUB_HOST=my\.git\.org git clone myproject 244 . 245 .fi 246 . 247 .IP "" 0 248 . 249 .SH "EXAMPLES" 250 . 251 .SS "git init" 252 . 253 .nf 254 255 $ git init \-g 256 > git init 257 > git remote add origin git@github\.com:YOUR_USER/REPO\.git 258 . 259 .fi 260 . 261 .SS "git push" 262 . 263 .nf 264 265 $ git push origin,staging,qa bert_timeout 266 > git push origin bert_timeout 267 > git push staging bert_timeout 268 > git push qa bert_timeout 269 270 $ git push origin 271 > git push origin HEAD 272 . 273 .fi 274 . 275 .SS "git checkout" 276 . 277 .nf 278 279 $ git checkout https://github\.com/jingweno/gh/pull/35 280 > git remote add \-f \-t feature git://github:com/foo/gh\.git 281 > git checkout \-\-track \-B foo\-feature foo/feature 282 283 $ git checkout https://github\.com/jingweno/gh/pull/35 custom\-branch\-name 284 . 285 .fi 286 . 287 .SS "git merge" 288 . 289 .nf 290 291 $ git merge https://github\.com/jingweno/gh/pull/73 292 > git fetch git://github\.com/jingweno/gh\.git +refs/heads/feature:refs/remotes/jingweno/feature 293 > git merge jingweno/feature \-\-no\-ff \-m \'Merge pull request #73 from jingweno/feature\.\.\.\' 294 . 295 .fi 296 . 297 .SS "git clone" 298 . 299 .nf 300 301 $ git clone jingweno/gh 302 > git clone git://github\.com/jingweno/gh 303 304 $ git clone \-p jingweno/gh 305 > git clone git@github\.com:jingweno/gh\.git 306 307 $ git clone jekyll_and_hype 308 > git clone git://github\.com/YOUR_LOGIN/jekyll_and_hype\. 309 310 $ git clone \-p jekyll_and_hype 311 > git clone git@github\.com:YOUR_LOGIN/jekyll_and_hype\.git 312 . 313 .fi 314 . 315 .SS "git fetch" 316 . 317 .nf 318 319 $ git fetch jingweno 320 > git remote add jingweno git://github\.com/jingweno/REPO\.git 321 > git fetch jingweno 322 323 $ git fetch jingweno,foo 324 > git remote add jingweno \.\.\. 325 > git remote add foo \.\.\. 326 > git fetch \-\-multiple jingweno foo 327 328 $ git fetch \-\-multiple jingweno foo 329 > git remote add jingweno \.\.\. 330 > git remote add foo \.\.\. 331 > git fetch \-\-multiple jingweno foo 332 . 333 .fi 334 . 335 .SS "git cherry\-pick" 336 . 337 .nf 338 339 $ git cherry\-pick https://github\.com/jingweno/gh/commit/a319d88#comments 340 > git remote add \-f jingweno git://github\.com/jingweno/gh\.git 341 > git cherry\-pick a319d88 342 343 $ git cherry\-pick jingweno@a319d88 344 > git remote add \-f jingweno git://github\.com/jingweno/gh\.git 345 > git cherry\-pick a319d88 346 347 $ git cherry\-pick jingweno@SHA 348 > git fetch jingweno 349 > git cherry\-pick SHA 350 . 351 .fi 352 . 353 .SS "git remote" 354 . 355 .nf 356 357 $ git remote add jingweno 358 > git remote add \-f jingweno git://github\.com/jingweno/CURRENT_REPO\.git 359 360 $ git remote add \-p jingweno 361 > git remote add \-f jingweno git@github\.com:jingweno/CURRENT_REPO\.git 362 363 $ git remote add origin 364 > git remote add \-f YOUR_USER git://github\.com/YOUR_USER/CURRENT_REPO\.git 365 . 366 .fi 367 . 368 .SS "git submodule" 369 . 370 .nf 371 372 $ git submodule add jingweno/gh vendor/gh 373 > git submodule add git://github\.com/jingweno/gh\.git vendor/gh 374 375 $ git submodule add \-p jingweno/gh vendor/gh 376 > git submodule add git@github\.com:jingweno/gh\.git vendor/gh 377 378 $ git submodule add \-b gh \-\-name gh jingweno/gh vendor/gh 379 > git submodule add \-b gh \-\-name gh git://github\.com/jingweno/gh\.git vendor/gh 380 . 381 .fi 382 . 383 .SS "git pull\-request" 384 . 385 .nf 386 387 # while on a topic branch called "feature": 388 $ git pull\-request 389 [ opens text editor to edit title & body for the request ] 390 [ opened pull request on GitHub for "YOUR_USER:feature" ] 391 392 # explicit pull base & head: 393 $ git pull\-request \-b jingweno:master \-h jingweno:feature 394 395 $ git pull\-request \-m "title\en\enbody" 396 [ create pull request with title & body ] 397 398 $ git pull\-request \-i 123 399 [ attached pull request to issue #123 ] 400 401 $ git pull\-request https://github\.com/jingweno/gh/pull/123 402 [ attached pull request to issue #123 ] 403 404 $ git pull\-request \-F FILE 405 [ create pull request with title & body from FILE ] 406 . 407 .fi 408 . 409 .SS "git apply" 410 . 411 .nf 412 413 $ git apply https://github\.com/jingweno/gh/pull/55 414 > curl https://github\.com/jingweno/gh/pull/55\.patch \-o /tmp/55\.patch 415 > git apply /tmp/55\.patch 416 417 $ git apply \-\-ignore\-whitespace https://github\.com/jingweno/gh/commit/fdb9921 418 > curl https://github\.com/jingweno/gh/commit/fdb9921\.patch \-o /tmp/fdb9921\.patch 419 > git apply \-\-ignore\-whitespace /tmp/fdb9921\.patch 420 421 $ git apply https://gist\.github\.com/8da7fb575debd88c54cf 422 > curl https://gist\.github\.com/8da7fb575debd88c54cf\.txt \-o /tmp/gist\-8da7fb575debd88c54cf\.txt 423 > git apply /tmp/gist\-8da7fb575debd88c54cf\.txt 424 . 425 .fi 426 . 427 .SS "git fork" 428 . 429 .nf 430 431 $ git fork 432 [ repo forked on GitHub ] 433 > git remote add \-f YOUR_USER git@github\.com:YOUR_USER/CURRENT_REPO\.git 434 435 $ git fork \-\-no\-remote 436 [ repo forked on GitHub ] 437 . 438 .fi 439 . 440 .SS "git create" 441 . 442 .nf 443 444 $ git create 445 \.\.\. create repo on github \.\.\. 446 > git remote add \-f origin git@github\.com:YOUR_USER/CURRENT_REPO\.git 447 448 # with description: 449 $ git create \-d \'It shall be mine, all mine!\' 450 451 $ git create recipes 452 [ repo created on GitHub ] 453 > git remote add origin git@github\.com:YOUR_USER/recipes\.git 454 455 $ git create sinatra/recipes 456 [ repo created in GitHub organization ] 457 > git remote add origin git@github\.com:sinatra/recipes\.git 458 . 459 .fi 460 . 461 .SS "git ci\-status" 462 . 463 .nf 464 465 $ git ci\-status 466 > (prints CI state of HEAD and exits with appropriate code) 467 > One of: success (0), error (1), failure (1), pending (2), no status (3) 468 469 $ git ci\-status \-v 470 > (prints CI state of HEAD, the URL to the CI build results and exits with appropriate code) 471 > One of: success (0), error (1), failure (1), pending (2), no status (3) 472 473 $ git ci\-status BRANCH 474 > (prints CI state of BRANCH and exits with appropriate code) 475 > One of: success (0), error (1), failure (1), pending (2), no status (3) 476 477 $ git ci\-status SHA 478 > (prints CI state of SHA and exits with appropriate code) 479 > One of: success (0), error (1), failure (1), pending (2), no status (3) 480 . 481 .fi 482 . 483 .SS "git browse" 484 . 485 .nf 486 487 $ git browse 488 > open https://github\.com/YOUR_USER/CURRENT_REPO 489 490 $ git browse commit/SHA 491 > open https://github\.com/YOUR_USER/CURRENT_REPO/commit/SHA 492 493 $ git browse issues 494 > open https://github\.com/YOUR_USER/CURRENT_REPO/issues 495 496 $ git browse \-p jingweno/gh 497 > open https://github\.com/jingweno/gh 498 499 $ git browse \-p jingweno/gh commit/SHA 500 > open https://github\.com/jingweno/gh/commit/SHA 501 502 $ git browse \-p resque 503 > open https://github\.com/YOUR_USER/resque 504 505 $ git browse \-p resque network 506 > open https://github\.com/YOUR_USER/resque/network 507 . 508 .fi 509 . 510 .SS "git compare" 511 . 512 .nf 513 514 $ git compare refactor 515 > open https://github\.com/CURRENT_REPO/compare/refactor 516 517 $ git compare 1\.0\.\.1\.1 518 > open https://github\.com/CURRENT_REPO/compare/1\.0\.\.\.1\.1 519 520 $ git compare \-u other\-user patch 521 > open https://github\.com/other\-user/REPO/compare/patch 522 . 523 .fi 524 . 525 .SS "git release (beta)" 526 . 527 .nf 528 529 $ git release 530 > (prints a list of releases of YOUR_USER/CURRENT_REPO) 531 532 $ git release TAG 533 > (creates a new release for the given tag) 534 . 535 .fi 536 . 537 .SS "git issues (beta)" 538 . 539 .nf 540 541 $ git issue 542 > (prints a list of issues for YOUR_USER/CURRENT_REPO) 543 544 $ git issue create 545 > (creates an issue for the project that "origin" remte points to) 546 . 547 .fi 548 . 549 .SH "BUGS" 550 \fIhttps://github\.com/github/gh/issues\fR 551 . 552 .SH "AUTHORS" 553 \fIhttps://github\.com/github/gh/contributors\fR 554 . 555 .SH "SEE ALSO" 556 git(1), git\-clone(1), git\-remote(1), git\-init(1), \fIhttp://github\.com\fR, \fIhttps://github\.com/github/hub\fR