- 10 May, 2017 1 commit
-
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 06 May, 2017 1 commit
-
-
blackst0ne authored
-
- 16 Mar, 2017 1 commit
-
-
Z.J. van de Weg authored
-
- 06 Mar, 2017 1 commit
-
-
Grzegorz Bizon authored
This makes it possible to maintain backwards compatibility with configs created when manual actions were non-blocking. From now manual actions are blocking if configured with `allow_failure: false`, otherwise manual actions are optional, and their status is ignored.
-
- 03 Mar, 2017 3 commits
-
-
Lin Jen-Shin authored
Also feedback in: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9666/diffs#note_24608283
- 02 Mar, 2017 1 commit
-
-
Lin Jen-Shin authored
* Replace Unspecified with a field so that it's less surprising * Define inspect for Node for easy debugging (and avoid building a very huge string potentially from built-in inspect) * Set default cache key to 'default'
-
- 23 Feb, 2017 8 commits
-
-
Douwe Maan authored
This reverts commit e00fb2bdc2090e9cabeb1eb35a2672a882cc96e9. # Conflicts: # .rubocop.yml # .rubocop_todo.yml # lib/gitlab/ci/config/entry/global.rb # lib/gitlab/ci/config/entry/jobs.rb # spec/lib/gitlab/ci/config/entry/factory_spec.rb # spec/lib/gitlab/ci/config/entry/global_spec.rb # spec/lib/gitlab/ci/config/entry/job_spec.rb # spec/lib/gitlab/ci/status/build/factory_spec.rb # spec/lib/gitlab/incoming_email_spec.rb
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 04 Feb, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 25 Jan, 2017 5 commits
-
-
Leandro Camargo authored
-
Leandro Camargo authored
-
Leandro Camargo authored
-
Leandro Camargo authored
-
Leandro Camargo authored
-
- 05 Jan, 2017 1 commit
-
-
Z.J. van de Weg authored
Until this commit, GitLab would check if the URL in your .gitlab-ci.yml would be valid and adressable. However, this approach is rather limited. To begin, the URL couldn't be http://example:$PORT/my-project, as the PORT value would be interpolated after checking if the URL was valid, which its not. Also this gem will limit the amount of protocols allowed. This commit doesn't check, at all, if the URL is valid. This is now the responsablilty of the user. In my opion this is right, as the user ultimately benefits from a correct URL, but also, its impossible to cover all cases.
-
- 22 Nov, 2016 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 18 Nov, 2016 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 14 Nov, 2016 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 06 Jun, 2016 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-