I'm working on a project that has a complex CI setup, and reaches more
than 30. Sometimes `hub ci-status` would report success when it was
still pending, which was very annoying.

per_page=100 is used in many other queries, and is the maximum that is
allowed without paging.

Explicitly setting `hub.protocol` to `git` or using `HUB_PROTOCOL=git`
still uses the `git` protocol.

Co-authored-by: Mislav Marohnić <mislav@github.com>

The docs at os/signal.Notify warn about this signal delivery loss bug at
https://golang.org/pkg/os/signal/#Notify, which says:

    Package signal will not block sending to c: the caller must ensure
    that c has sufficient buffer space to keep up with the expected signal
    rate. For a channel used for notification of just one signal value,
    a buffer of size 1 is sufficient.

Caught by a static analysis tool from Orijtech, Inc. called "sigchanyzer"

Go 1.13: `Post <URL>: <message>`
Go 1.14: `Post "<URL>": <message>`

Since we have an existing test that includes this error message, make
sure that `url.Error`s are output without quotes around the URL.

This affects reading the current branch as well as reading the default
branch for a remote. Because we're no longer trying to read the ref
manually from the filesystem, this approach works with git worktrees.

Ensure that all flags are forwarded to `git version`

Fixes #2440

https://github.com/github/hub/runs/397657829

…enge

These should be helpful for debugging purposes.

Go's `net/http` will intentionally change the HTTP method being used
after a 301, 302, or 303 redirect for a non-GET request.

When encountering a 301 or 302 response codes, fail any non-GET request
with an tip that 308 and 307 should be used, respectively.

use strings.EqualFold instead of strings.ToLower with equal
operation when comparing string ignore case

Only ever dump HTTP request/response bodies if they are of the following
types:
- `text/*`
- `application/json` or `*+json`

Allows using `HUB_VERBOSE=1 hub release create -a <file>` to debug
attaching binary assets.

See #2379

Fixes #2197

Fixes #2315

Support HTTPS_PROXY, NO_PROXY from environment