Arch Linux has hub in its official repository. But I spent an hour installing go and other things because I thought hub would not be in the official repository.
The only thing that has substansively changed is that Go 1.8 handles
redirect logic more safely than previous versions. This means we can
drop our special handling to avoid following redirects to other
domains. We were only doing that to protect against the possibility
of leaking auth headers. With Go 1.8, the auth headers are not
forwarded when following a redirect to another domain, so we don't
need our special handling any more.
As long as people are attempting to build with the Makefile, the new
check_go_version script should cause the build to stop if our
collaborators aren't using at least version 1.8 of go.
These are very old projects from another time. Today, it doesn't make
sense to try to list similar projects, as they are easily discoverable
through other means. In the recent years, hub hasn't taken direct
inspiration from projects other than git.
Closes#1345
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.
Technically, anything in the third argument is passes as a string, so you can look at any file if you know the hash (for instance, `blob/HASH/app/index.js`. However, having the issue number passed seems to me to be something really useful to my workflow, so I was hoping to find something in the documentation about it.
Another possibility would be to enable a fourth argument for issue number. I'm happy to do a PR for this if something things it might be of more worth than just this edit.
- Ruby is not required at runtime anymore
- Most installation instructions are now obsolete. Will need to write
new instructions when we distribute precompiled binaries.
- Remove tedious parts about slowness. It's not slow anymore!
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.
Don't suggest standalone install via curl anymore because:
- hub may not be a single script in the near future
- `rake install` handles the Windows executable as well