This allows gitlab-shell to be called with an argument of the format
`key-123` or `username-name`.

When called in this way, `gitlab-shell` will call the GitLab internal
API. If the API responds with user information, it will print a
welcome message including the username.

If the API responds with a successful but empty response, gitlab-shell
will print a welcome message for an anonymous user.

If the API response includes an error message in JSON, this message
will be printed to stderr.

If the API call fails, an error message including the status code will
be printed to stderr.

Get secret from config

See merge request gitlab-org/gitlab-shell!284

This adds parsing if the `secret_file` from YAML. And reads the
contents of the configured file.

If no file is configured, we fall back to the `.gitlab_shell_secret`
in the root dir of the configuration.

If the configured path does not start with a `/` we start looking for
the file relative to the root dir of the configuration.

Release v8.7.1

See merge request gitlab-org/gitlab-shell!281

Fix unmarshalling JSON from the command line

See merge request gitlab-org/gitlab-shell!280

Release v8.7.0

See merge request gitlab-org/gitlab-shell!279

Add distributed tracing to GitLab-Shell

See merge request gitlab-org/gitlab-shell!277

Adds distributed tracing instrumentation to GitLab-Shell using LabKit

Update readme notes about git hooks

See merge request gitlab-org/gitlab-shell!278

Done using `govendor fetch -v gitlab.com/gitlab-org/labkit/...@master`

Release v8.6.0

See merge request gitlab-org/gitlab-shell!276

Add support for using gl_project_path

See merge request gitlab-org/gitlab-shell!275

This will enable us to track the human-readable project path with SSH
access in gitlab-shell. Currently the Gitaly logs will only show the
hashed storage and gl_repository path (e.g. project-1234).

Merge branch '57353-git-push-fails-on-large-lfs-files-where-the-push-take-a-long-time' into 'master'

Provide expires_in for LFS if available

See merge request gitlab-org/gitlab-shell!273

Bump gitaly-proto to v1.10.0

See merge request gitlab-org/gitlab-shell!274

This is done to ensure we don't run into unknown fields as we saw
in https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/364.

Parse commands to enable feature flags

See merge request gitlab-org/gitlab-shell!270

When SSH_CONNECTION is not set, we don't fall back to ruby, but
instead fail directly in go writing the error to stderr.

This adds the possibility to enable features for GitLab shell.

The first feature being recognized is "Discover": It's the command
that is executed when running `ssh git@gitlab.example.com` and is
called without a command.

The gitlab key id or username is already parsed from the command line
arguments.

Currently we only support communicating with GitLab-rails using unix
sockets. So features will not be enabled if the GitLab-url is using a
different protocol. The url for this read from the config yaml.

Pending ruby-specs have been added for the gitlab-shell command.

Refactor to have separate command packages

Add testify as test helpers

Force install bunder

See merge request gitlab-org/gitlab-shell!272

This avoids errors like:

$ gem install --bindir /usr/local/bin bundler -v "$INSTALL_BUNDLER_VERSION"
ERROR:  Error installing bundler:
	"bundle" from bundler conflicts with /usr/local/bin/bundle

Remove unused vendored code

See merge request gitlab-org/gitlab-shell!265

Specify bundler 1.17 for ruby 2.1 and 2.2

See merge request gitlab-org/gitlab-shell!271

Make better use of constants in lib/gitlab_shell.rb

See merge request gitlab-org/gitlab-shell!269

Gitaly hook transistion changes

See merge request gitlab-org/gitlab-shell!268

Fix rspec deprecation warning

See merge request gitlab-org/gitlab-shell!267

Fix spec failure with Ruby 2.5

See merge request gitlab-org/gitlab-shell!266