For the longest time I was assuming that this was a whitespace change
with `git diff`, even though I had fixed it when building this a few
weeks back, so I decided to not bother adding it to the previous
commits.  When I removed it and re-ran the tests, things stopped
working... oops :)

Implements the GeneratePRTemplate in pull_request.go instead of the
custom logic that previously existed in the file.  Addresses:

* Title being defaulted as the first line of the template
* Commit messages not defaulting as the title only properly

This allows the github.GeneratePRTemplate() function to autofill the
pull request title for a single commit pull request with either:

* The entire commit message, if it is a single line commit message
* The first line of the commit message, if it is a multi-line commit
  message

As far as the code is concerned, both cases above are interpreted in the
same fashion, but the expectations of the user are defined with each of
the new test cases in github/template_test.go

FYI, this commit message would be an example of a multi line commit
message :)

The function of this method is to defer the logic of generating a commit
message to template.go, and eventually remove that logic from
commands/pull_request.go

Also adds tests for this new method, which also modifies the
fixtures/test_repo.go file to accomidate a test repo with a `.github` PR
dir.

bashcomp: try to load git comp first (fix #592)

Closes #1139, fixes #1100

Instead of per-request approach of invoking `client.requestURL()`
manually whenever we're constructing a request path, simply define the
`/api/v3` prefix when configuring the API root URL for `simpleApi` client.

Fix copy-pasta

The description for --head said it was the head branch instead of head branch.

Git Hub Enterprise requests should always include /api/v3 in the URL
in order to hit the correct API endpoint. The ci-status and release
commands were producing the wrong request URL. As result, an LDAP
authentication page was returned rather than the expected JSON. A
parsing error could be seen: "invalid character '<' looking for beginning
of value".

This commit changes the construction of the request URL for the
ci-status and release commands, making sure the existing client.requestURL
function is called. This makes sure the API request hits always hits the
right endpoint in Git Hub Enterprise.

The `create` and `remote` commands needs to infer the current project
name from the project's directory. Instead of using the current working
directory, which doesn't necessarily match the project's toplevel
directory, use `git rev-parse --show-toplevel` which also respects the
`-C` global flag setting.

Fixes #1105, closes #1114

Fixes #1125, closes #1126

Add `hub release download` command that downloads all assets.

Make tests more robust to various Locales.

Prompt for user when the config has a token but no user. Fixes #1007

Don't use octokit in GhLatestTagName.

Fixes #1105

For git commands that are extended by hub, such as `git remote`, the
final git command would get executed without the git global flags
provided when executing hub in the first place.

This most notably broke the usage of `-C <dir>` flag.

Big overhaul of `hub release` command

Filter project issues by assignee