- 07 7月, 2018 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 08 6月, 2018 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 19 3月, 2018 1 次提交
-
-
由 Andreas Baumann 提交于
-
- 06 9月, 2017 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 12 9月, 2016 1 次提交
-
-
由 Mislav Marohnić 提交于
Ported from my bash version over at https://github.com/mislav/dotfiles/blob/370154a5adc482afd89606c126bcd18df2560013/bin/git-sync
-
- 21 8月, 2016 2 次提交
-
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
- 24 1月, 2016 2 次提交
-
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Man pages should be the canonical source of hub documentation. People should use `man help hub` instead of viewing the README, which might not even correspond to the version they have installed. This ends the confusing man page build system in which parts of the README are injected into `hub.1.ronn` source file, deletes the Rakefile and removes rake from gem bundle. The examples are deleted because they are now inlined with individual command documentation. So did the documentation for all hub commands get deleted from main man page in favor of individual man pages. However, this makes main man page have absolutely no listing of which commands are available. This will get addressed as we go forward.
-
- 27 9月, 2015 3 次提交
-
-
由 Mislav Marohnić 提交于
Now `ci-status` consumes the new combined statuses API endpoint designed for when multiple contexts report statuses independently. The verbose output is now colorized and is in format where each line is:
✔ ︎<Tab>[CONTEXT]<Tab>[URL] -
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
[ci skip]
-
- 07 8月, 2015 1 次提交
-
-
由 David Calavera 提交于
Signed-off-by: NDavid Calavera <david.calavera@gmail.com>
-
- 14 5月, 2015 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 07 4月, 2015 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 08 1月, 2015 1 次提交
-
-
- 30 10月, 2014 1 次提交
-
-
由 Jingwen Owen Ou 提交于
-
- 28 10月, 2014 1 次提交
-
-
由 Jingwen Owen Ou 提交于
-
- 27 2月, 2014 1 次提交
-
-
由 Tomas Varneckas 提交于
-
- 22 12月, 2013 2 次提交
-
-
由 Mislav Marohnić 提交于
Since cloning of private repos over `git:` protocol is not possible, users were required to manually add the `-p` flag to trigger cloning over the `ssh:` protocol. Now, use the GitHub API to obtain information about the repo to be cloned, and automatically use the `ssh:` protocol if the repo is private or if the current user has push access to that repo. Fixes #212, fixes #213
-
由 Mislav Marohnić 提交于
This feature is likely to get dropped from GitHub API in the near future. The alternative is to simply create a new pull-request and reference the original issue in the description.
-
- 14 12月, 2013 1 次提交
-
-
由 Mislav Marohnić 提交于
All parameters are optional. Fixes #290 [ci skip]
-
- 29 10月, 2013 1 次提交
-
-
由 Kirill Müller 提交于
Fixes #422, closes #423
-
- 10 7月, 2013 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 21 6月, 2013 1 次提交
-
-
由 Adam Spiers 提交于
-
- 13 5月, 2013 1 次提交
-
-
由 Mislav Marohnić 提交于
Emulates the interface of `git commit`: $ hub pull-request -m "This is my title" $ hub pull-request -F /path/to/message.txt $ hub pull-request -F - The old way of passing in just title is deprecated $ hub pull-request "Deprecated title" Fixes #183
-
- 27 4月, 2013 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 23 11月, 2012 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 07 5月, 2012 2 次提交
-
-
由 Mislav Marohnić 提交于
It doesn't add a remote anymore, as it isn't needed.
-
由 John Firebaugh 提交于
It does what GitHub's "Merge pull request" button does: merges the pull request with a nice commit message that includes the pull request ID and title. Like `hub checkout`, it creates a remote, but it does not create a local branch.
-
- 05 5月, 2012 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 21 3月, 2012 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 20 3月, 2012 1 次提交
-
-
由 Mislav Marohnić 提交于
-
- 03 1月, 2012 2 次提交
-
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
- 24 11月, 2011 5 次提交
-
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Closes #75
-
由 Mislav Marohnić 提交于
-