delta/gitlab/gitlab-shell.git - gitlab.com: gitlab-org/gitlab-shell.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Move go code up one level	Nick Thomas	2019-10-18	1	-112/+0
\|
*	Remove feature flags and the fallback command	Nick Thomas	2019-09-20	1	-71/+0
\|
*	Support calling internal API using HTTPS	Igor	2019-05-01	1	-2/+9
\|
*	Support calling internal api using HTTP	Igor	2019-04-24	1	-6/+24
\|
*	Get secret from config	Bob Van Landuyt	2019-03-13	1	-26/+68
\| \| \| \| \| \| \| \| \| \| \|	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.
*	Allow enabling gitlab-shell "discover"-feature	Bob Van Landuyt	2019-01-15	1	-0/+63
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	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
*	Allow the config directory to be specified	Nick Thomas	2018-09-28	1	-1/+1
\|
*	Specify a richer scheme to run the migration with	Nick Thomas	2018-09-28	1	-7/+17
\|
*	Initial feature-flagged go/ruby switch	Nick Thomas	2018-09-28	1	-3/+9
\|
*	Switch to structured logging	Jacob Vosmaer (GitLab)	2018-03-19	1	-12/+21
\|
*	Use gitaly-upload-pack and gitaly-receive-pack	Jacob Vosmaer	2017-05-23	1	-0/+28