print_warnings is now using that method in order to print a large
formatted warning message, so renaming the method to be less tied to
the broadcast message functionality.

Warnings are printed using the same method that prints broadcast
messages. This ensures that whatever warnings are returned will be
displayed correctly.

Update readme notes about git hooks

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

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

Handle push options

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

See the discussion on gitlab-org/gitlab-shell!166

https://github.com/rubocop-hq/ruby-style-guide#module-function

push_opts[] is named as such so that it becomes an array in the
GitLab internal Grape::API params hash. If it were named push_opts, only
the final (scalar) push_opts parameter would be present.

Also update specs to include push_opts parameter:
- gitlab_post_receive_spec
- gitlab_net_spec for the internal API change

This module is responsible for converting the GIT_PUSH_OPTION_*
environment variables into an array.

See https://gitlab.com/gitlab-org/gitlab-ce/issues/18667

Remove unused lib/names_helper.rb

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

This reverts merge request !257