- 24 2月, 2019 4 次提交
-
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Make `checkout` work independently of remote refspec
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
This fixes: fatal: Cannot setup tracking information; starting point 'BRANCH' is not a branch. if the remote refspec is set up to only fetch specific branches and NOT like the default `+refs/heads/*:refs/remotes/origin/*`. I don't understand why would git, after fetching into `refs/remotes/origin/BRANCH`, complain that `origin/BRANCH` is not a branch, but there we have it. Setting up upstream tracking manually works around this problem.
-
- 22 2月, 2019 3 次提交
-
-
由 Mislav Marohnić 提交于
Add pull-request --no-edit flag to zsh completion
-
由 Mislav Marohnić 提交于
Documentation of install on Debian (sid/buster)
-
由 Cody Allen 提交于
-
- 21 2月, 2019 2 次提交
-
-
由 Kim Hansen 提交于
Squash on merge
-
由 Mislav Marohnić 提交于
Ref. #2043
-
- 20 2月, 2019 1 次提交
-
-
由 Kim Hansen 提交于
Fixes #718 by documenting that the package is in the official repository now, or perhaps there is also a need for a package for the current stable Debian version.
-
- 19 2月, 2019 1 次提交
-
-
由 Mislav Marohnić 提交于
List PR "Draft" state using the `--format` string
-
- 18 2月, 2019 7 次提交
-
-
由 Mislav Marohnić 提交于
- `%pS`: "open", "draft", "merged", or "closed" - `%pC`: green, gray, purple, or red
-
由 Mislav Marohnić 提交于
Have commands with rich output respect the `--color` flag
-
由 Mislav Marohnić 提交于
Add FreeBSD installation instructions
-
由 Mislav Marohnić 提交于
Make man pages parseable with `whatis`
-
由 Mislav Marohnić 提交于
- default: `--color=auto` - `--color` is equivalent to `--color=always` - `--color=never` disables color for TTYs
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Outputs the "NAME" section in roff format to fix the following: mandb: warning: ... whatis parse for hub-alias(1) failed
-
- 15 2月, 2019 1 次提交
-
-
由 Mateusz Piotrowski 提交于
-
- 13 2月, 2019 6 次提交
-
-
由 Mislav Marohnić 提交于
-
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
-
由 Mislav Marohnić 提交于
Assume that 4xx responses will be the same given the same request, so these responses should be subject to caching too. Avoids caching 403 because that is the status returned when GitHub API limit is hit. Continue not caching 5xx responses because they indicate server errors, so it's possible that a 2nd request of identical parameters succeeds.
-
- 09 2月, 2019 1 次提交
-
-
由 Paul Gierz 提交于
-
- 07 2月, 2019 4 次提交
-
-
由 Mislav Marohnić 提交于
Allow raw request body via `hub api --input <FILE>`
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Fixes #2022
-
- 30 1月, 2019 3 次提交
-
-
由 Mislav Marohnić 提交于
Consistent ordering and `--format` support for `ci-status`
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Statuses are now sorted the same as in the GitHub web interface: - failing first; - then pending; - then success/neutral; - everything in-between is sorted alphabetically. Fixes #2021
-
- 29 1月, 2019 2 次提交
-
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Add HTTP request/response headers functionality to `hub api`
-
- 28 1月, 2019 5 次提交
-
-
由 Mislav Marohnić 提交于
Fix subcommand execution under WSL
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
Makefile: fix arguments to go, not matching what go expects
-
由 Mislav Marohnić 提交于
-
由 Mislav Marohnić 提交于
- HTTP response is now printed on stdout regardless of HTTP status - No longer print an extra newline after HTTP response body - No more `Error: HTTP {STATUS}` message on stderr - hub exits with status 22 instead of 1
-