The `gist show --json` representation wasn't the full JSON payload of
a gist. For programmatic use of gists, `hub api` is better:
hub api gists/:id | jq '.files | keys'
This will output JSON exactly as it's received from the API and it frees
us from having to reimplement parts of this functionality within `gist`.
If hub is configured with multiple hosts (usually including GitHub
Enterprise instances), every invocation to `hub gist` would prompt to
select a host. Assume that people want to use the first configured host
by default (they can change it via GITHUB_HOST).
This addresses #2226 and #2116 by creating a `gist` subcommand.
This allows you to both create and retrieve gists. When creating a gist
it can be public or private.
In order to do this, the `gist` scope is added to the token we request.
Closes: #2226Closes: #2116
Signed-off-by: Phil Dibowitz <phil@ipom.com>