- 07 4月, 2017 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 06 4月, 2017 3 次提交
-
-
由 Jarka Kadlecova 提交于
-
由 Sean McGivern 提交于
Don’t show source project name when user does not have access See merge request !2081
-
由 Lin Jen-Shin 提交于
whenever the feature is disabled in the project.
-
- 05 4月, 2017 9 次提交
-
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
-
由 Rydkin Maxim 提交于
fix changelog MR reference add non-HEAD builds finder and add `created` pipelines to scope add spec for auto-cancel non-HEAD pipelines and refactor create_pipeline_service_spec more refactoring for spec adds option for auto-cancel into CI/CD settings fix spec to new configuration fix rubocop fix schema.rb fix schema.rb replace Gitlab 9.0 with 9.1 in doc change wording on pipeline settings added auto_canceled_by field as identifier of autocancel subject remove unnecessary index replace service with retry_lock replace auto_cancel_pending_pipelines boolean setting with integer (and enum in model) fix schema.rb fix schema.rb remove projekt attribute and clean up spec clean up spec withcouple of shared examples added spec for "It does not cancel current pipeline" scenario add some specs to auto-cancel add spec for another branch pipelines
-
由 DJ Mountney 提交于
This param is passed to service in two places, one is in the build_user for non ldap oauth users. And the other is in the initial production admin user seed data. Without this change, when setting up GitLab in a production environment, you were not being given the option of setting the root password on initial setup in the UI.
-
- 04 4月, 2017 2 次提交
-
-
由 Jarka Kadlecova 提交于
-
-
- 03 4月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
1. Never send a pipeline email to anyone other than the user who created the pipeline. 2. Only send pipeline success emails to people with the custom notification setting for enabled. Watchers and participants will never receive this. 3. When custom settings are unset (for new settings and legacy ones), act as if failed_pipeline is set.
-
- 02 4月, 2017 2 次提交
-
-
由 Stan Hu 提交于
When deleting a user, the following sequence could happen: 1. Project `mygroup/myproject` is scheduled for deletion 2. The group `mygroup` is deleted 3. Sidekiq worker runs to delete `mygroup/myproject`, but the namespace and routes have been destroyed. Closes #30334
-
由 Grzegorz Bizon 提交于
-
- 31 3月, 2017 1 次提交
-
-
由 Dongqing Hu 提交于
-
- 30 3月, 2017 2 次提交
-
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Sean McGivern 提交于
Prevent private group disclosure via parent_id See merge request !2077
-
- 29 3月, 2017 3 次提交
-
-
由 Jarka Kadlecova 提交于
-
由 Dongqing Hu 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 28 3月, 2017 3 次提交
-
-
由 Jarka Kadlecova 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Robert Speicher 提交于
-
- 27 3月, 2017 2 次提交
-
-
由 George Andrinopoulos 提交于
-
由 Grzegorz Bizon 提交于
-
- 25 3月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 24 3月, 2017 1 次提交
-
-
由 blackst0ne 提交于
-
- 23 3月, 2017 2 次提交
-
-
由 Jarka Kadlecova 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 22 3月, 2017 1 次提交
-
-
由 Oswaldo Ferreira 提交于
-
- 21 3月, 2017 2 次提交
-
-
由 Adam Niedzielski 提交于
Closes #29687
-
由 Douwe Maan 提交于
Protect server against SSRF in project import URLs See merge request !2068
-
- 18 3月, 2017 2 次提交
-
-
由 Kamil Trzciński 提交于
-
由 Dongqing Hu 提交于
-
- 17 3月, 2017 2 次提交
-
-
由 Adam Niedzielski 提交于
Closes #28890
-
由 Alex Sanford 提交于
-