- 01 Apr, 2019 1 commit
-
-
Rémy Coutable authored
Add pry gem to allow easy debugging See merge request gitlab-org/gitlab-shell!289
-
- 28 Mar, 2019 1 commit
-
-
Luke Duncalfe authored
-
- 21 Mar, 2019 2 commits
-
-
Nick Thomas authored
Provide go implementation for 2fa_recovery_codes command See merge request gitlab-org/gitlab-shell!285
-
Igor authored
-
- 19 Mar, 2019 1 commit
-
-
Nick Thomas authored
Better testing for JSON deserialisation See merge request gitlab-org/gitlab-shell!282
-
- 18 Mar, 2019 1 commit
-
-
Andrew Newdigate authored
Adds tests to ensure that JSON deserialisation from program arguments takes place. This was a testing blind spot, which led to a brief regression: https://gitlab.com/gitlab-org/gitlab-shell/merge_requests/280
-
- 15 Mar, 2019 2 commits
-
-
Nick Thomas authored
Call gitlab "/internal/discover" from go Closes #175 See merge request gitlab-org/gitlab-shell!283
-
Bob Van Landuyt authored
The reporter struct can be used for passing around and reporting to the io.Writer of choice.
-
- 14 Mar, 2019 1 commit
-
-
Bob Van Landuyt authored
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.
-
- 13 Mar, 2019 3 commits
-
-
Nick Thomas authored
Get secret from config See merge request gitlab-org/gitlab-shell!284
-
Bob Van Landuyt authored
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.
-
Bob Van Landuyt authored
-
- 06 Mar, 2019 6 commits
-
-
Nick Thomas authored
Release v8.7.1 See merge request gitlab-org/gitlab-shell!281
-
Nick Thomas authored
-
Stan Hu authored
Fix unmarshalling JSON from the command line See merge request gitlab-org/gitlab-shell!280
-
Nick Thomas authored
-
Nick Thomas authored
Release v8.7.0 See merge request gitlab-org/gitlab-shell!279
-
Nick Thomas authored
-
- 04 Mar, 2019 1 commit
-
-
Nick Thomas authored
Add distributed tracing to GitLab-Shell See merge request gitlab-org/gitlab-shell!277
-
- 01 Mar, 2019 1 commit
-
-
Andrew Newdigate authored
Adds distributed tracing instrumentation to GitLab-Shell using LabKit
-
- 28 Feb, 2019 2 commits
-
-
Douwe Maan authored
Update readme notes about git hooks See merge request gitlab-org/gitlab-shell!278
-
Jacob Vosmaer authored
-
- 26 Feb, 2019 1 commit
-
-
Andrew Newdigate authored
-
- 25 Feb, 2019 1 commit
-
-
Andrew Newdigate authored
Done using `govendor fetch -v gitlab.com/gitlab-org/labkit/...@master`
-
- 19 Feb, 2019 2 commits
-
-
Nick Thomas authored
Release v8.6.0 See merge request gitlab-org/gitlab-shell!276
-
Stan Hu authored
-
- 18 Feb, 2019 1 commit
-
-
Nick Thomas authored
Add support for using gl_project_path See merge request gitlab-org/gitlab-shell!275
-
- 16 Feb, 2019 1 commit
-
-
Stan Hu authored
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).
-
- 14 Feb, 2019 3 commits
-
-
Robert Speicher authored
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
-
Nick Thomas authored
Bump gitaly-proto to v1.10.0 See merge request gitlab-org/gitlab-shell!274
-
Ash McKenzie authored
-
- 13 Feb, 2019 1 commit
-
-
Stan Hu authored
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.
-
- 15 Jan, 2019 3 commits
-
-
Nick Thomas authored
Parse commands to enable feature flags See merge request gitlab-org/gitlab-shell!270
-
Bob Van Landuyt authored
When SSH_CONNECTION is not set, we don't fall back to ruby, but instead fail directly in go writing the error to stderr.
-
Bob Van Landuyt authored
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
-
- 14 Jan, 2019 1 commit
-
-
Bob Van Landuyt authored
Add testify as test helpers
-
- 09 Jan, 2019 2 commits
-
-
Nick Thomas authored
Force install bunder See merge request gitlab-org/gitlab-shell!272
-
Bob Van Landuyt authored
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
-
- 07 Jan, 2019 1 commit
-
-
Nick Thomas authored
Remove unused vendored code See merge request gitlab-org/gitlab-shell!265
-
- 04 Jan, 2019 1 commit
-
-
Douwe Maan authored
Specify bundler 1.17 for ruby 2.1 and 2.2 See merge request gitlab-org/gitlab-shell!271
-