If you're trying to create `owner/foo` repo and there is an existing
redirect from `owner/foo` to a differently name repo, don't consider
that one as an existing repo and proceed with creating `owner/foo`.

Prevent setting a public upstream when creating a private repo.

Fixes #1854

https://github.com/github/hub/issues/1849

Handle case of `.github/ISSUE_TEMPLATE` directory

Fixes #1813 [ci skip]

Ignore the directory of multiple issue templates for now. In the future,
there might be a way to pick a specific template from the list; this
change is just to prevent crashes.

Fixes #1822

Handle more cases when Checks API is unavailable

Avoid re-requesting reviewers in case of CODEOWNERS

Fixes #1837

Older Enterprise hosts won't have Checks API, but we still want `hub
ci-status` to work with them. It seems like a HTTP 403 is returned in
that case, so we can safely ignore it. Also ignore HTTP 404 just in case.

Fixes #1821

It wasn't necessary for github.com since December 2017.

Requesting a review via `hub pull-request -r foo` would print a
misleading error message that `foo` couldn't be requested for review in
case `foo` was already requested per CODEOWNERS.

Fixes #1840

This is to avoid a crash in Unmarshal. #1840

Update link to code of conduct

`hub init` doesn't imply `hub create`. I've written wrong documentation
in 0a45aa8d

Fixes #1810

The `hub` package is out of date and repeated attempts to contact the
maintainer and take over the package have failed.

https://chocolatey.org/packages/hub
https://github.com/github/hub/issues/1288
https://github.com/twsouthwick/github-hub-chocolatey/issues/1

Have `ci-status` also query Checks API

The results of Status and Checks API are merged together.

Fixes #1787

Fix integration with git 2.18 shell completions

Wrap `git --list-cmds=others` command used by git built-in shell
completions to add a list of hub custom commands.

Fixes #1792

Fix example for fetch.

Add documentation link to Readme

[ci skip]