When a remote user with a valid SSH key runs something like 'ssh
git@gitlab.example.com foobar', gitlab-shell would raise an exception in
the GitlabShell#escape_path method. With this change, we catch an
invalid number of arguments as soon as possible and exit.

Update changelog

in light of !35

See merge request !36

Abort check path

Fixes #13

See merge request !35

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Fix repository name/path extraction for GitlabUpdate

See merge request !34

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Update README Markdown style to match CONTRIBUTING

Adding support+tests for annotated tags.

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Use simplecov for development.

GitlabUpdate: use stripped path for repo_name

Improve coverage.

Use a default for gitlab_url that usually works

This default lets gitlab-shell connect to Unicorn directly, instead of
going through Nginx. This has the following benefits:

- the majority of users no longer has to edit the `gitlab_url`;
- avoid issues when the external GitLab web address does not resolve on
  the GitLab server itself;
- avoid SSL certificate issues.

See merge request !32

Expliclity require 'timeout' from the stdlib

This avoids getting the following error on some platforms:

NameError: uninitialized constant GitlabKeys::Timeout

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Use lock file when add new entries to authorized_keys

Fixes #21

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Lock file location

Authorized keys lock

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>