- 04 4月, 2018 1 次提交
-
-
由 Jan 提交于
-
- 28 3月, 2018 4 次提交
-
-
由 Tomasz Maczukin 提交于
-
由 Tomasz Maczukin 提交于
-
由 Tomasz Maczukin 提交于
-
由 Tomasz Maczukin 提交于
-
- 07 3月, 2018 2 次提交
-
-
由 Bob Van Landuyt 提交于
-
由 Jan Provaznik 提交于
* adds basic discussions API for issues and snippets * reorganizes notes specs (so same tests can be used for all noteable types - issues, MRs, snippets)
-
- 06 3月, 2018 2 次提交
-
-
由 Travis Miller 提交于
-
由 Francisco Javier López 提交于
-
- 03 3月, 2018 1 次提交
-
-
由 haseeb 提交于
-
- 01 3月, 2018 2 次提交
-
-
由 Jean-Baptiste Guerraz 提交于
-
由 Travis Miller 提交于
-
- 28 2月, 2018 1 次提交
-
-
由 haseeb 提交于
-
- 23 2月, 2018 1 次提交
-
-
由 Nick Thomas 提交于
-
- 14 2月, 2018 2 次提交
-
-
由 Robert Schilling 提交于
-
由 Jarka Kadlecová 提交于
-
- 13 2月, 2018 2 次提交
-
-
由 James Lopez 提交于
-
由 James Lopez 提交于
-
- 10 2月, 2018 1 次提交
-
-
由 Robert Schilling 提交于
-
- 09 2月, 2018 2 次提交
-
-
由 Robert Schilling 提交于
-
由 Robert Schilling 提交于
-
- 08 2月, 2018 1 次提交
-
-
由 Markus Koller 提交于
-
- 06 2月, 2018 1 次提交
-
-
由 Jarka Kadlecová 提交于
-
- 31 1月, 2018 1 次提交
-
-
由 Stan Hu 提交于
We can simplify the code quite a bit and improve performance by using grape-entity merge fields: https://github.com/ruby-grape/grape-entity/tree/v0.6.0#merge-fields Relates to #42030
-
- 30 1月, 2018 1 次提交
-
-
由 Oswaldo Ferreira 提交于
-
- 29 1月, 2018 1 次提交
-
-
由 Oswaldo Ferreira 提交于
-
- 25 1月, 2018 1 次提交
-
-
由 Douwe Maan 提交于
This reverts merge request !16626
-
- 24 1月, 2018 3 次提交
-
-
由 Toon Claes 提交于
To make it more clear to developers that the entity exposes the application secret, define a separate entity that only should be used when the secret is needed (probably only on creation).
-
由 Nicolas MERELLI 提交于
-
由 Oswaldo Ferreira 提交于
-
- 17 1月, 2018 2 次提交
-
-
由 Douwe Maan 提交于
[10.3] Migrate `can_push` column from `keys` to `deploy_keys_project` See merge request gitlab/gitlabhq!2276 (cherry picked from commit f6ca52d31bac350a23938e0aebf717c767b4710c) 1f2bd3c0 Backport to 10.3
-
由 Stan Hu 提交于
Merge branch 'security-10-3-do-not-expose-passwords-or-tokens-in-service-integrations-api' into 'security-10-3' Filter out sensitive fields from the project services API See merge request gitlab/gitlabhq!2281 (cherry picked from commit 476f2576444632f2a9a61b4cead9c1077f2c81d7) 2bcbbda0 Filter out sensitive fields from the project services API
-
- 09 1月, 2018 2 次提交
-
-
由 Francisco Javier López 提交于
-
由 Yorick Peterse 提交于
This removes all usage of soft removals except for the "pending delete" system implemented for projects. This in turn simplifies all the query plans of the models that used soft removals. Since we don't really use soft removals for anything useful there's no point in keeping it around. This _does_ mean that hard removals of issues (which only admins can do if I'm not mistaken) can influence the "iid" values, but that code is broken to begin with. More on this (and how to fix it) can be found in https://gitlab.com/gitlab-org/gitlab-ce/issues/31114. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37447
-
- 05 1月, 2018 2 次提交
-
-
由 Alessio Caiazza 提交于
-
由 Felipe Artur 提交于
-
- 04 1月, 2018 2 次提交
-
-
由 Alexis Reigel 提交于
-
由 Luc Didry 提交于
-
- 03 1月, 2018 1 次提交
-
-
由 Alessio Caiazza 提交于
-
- 22 12月, 2017 1 次提交
-
-
由 Mark Fletcher 提交于
+ Add support for the new separate channel and events settings * Dry up chat notifications in the service properties definitions
-