- 02 11月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
Because this code resides in lib/ it may be eager loaded. Rails in turn doesn't define Rails::Generators by default unless you explicitly require "rails/generators".
-
- 01 11月, 2016 2 次提交
-
-
由 Felipe Artur 提交于
-
-
- 31 10月, 2016 2 次提交
-
-
由 Z.J. van de Weg 提交于
-
由 Yorick Peterse 提交于
These are regular Rails migrations that are executed by default. A user can opt-out of these migrations by setting an environment variable during the deployment process. Fixes gitlab-org/gitlab-ce#22133
-
- 29 10月, 2016 2 次提交
-
-
由 winniehell 提交于
-
由 Alejandro Rodríguez 提交于
When we updated gitlab_git to 10.4.1, `tag.target` changed from pointing to the sha of the tag to the sha of the commit the tag points to. The problem is that only annotated tags have `object_sha`s, lightweight tags don't (it's nil), so (only) in their case we still need to use `tag.target`.
-
- 28 10月, 2016 8 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 winniehell 提交于
-
由 Adam Niedzielski 提交于
Do not pass project.owner because it may return a group and Labels::FindOrCreateService throws an error in this case. Fixes #23694.
-
由 Ahmad Sherif 提交于
-
由 Ahmad Sherif 提交于
-
由 Ahmad Sherif 提交于
-
由 Ahmad Sherif 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 27 10月, 2016 5 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Ahmad Sherif 提交于
-
由 Ahmad Sherif 提交于
-
由 Kamil Trzcinski 提交于
-
由 tiagonbotelho 提交于
only.
-
- 26 10月, 2016 6 次提交
-
-
由 Joshua Welsh 提交于
When adding a deploy key that already exists in the project the existing key would not be returned, resulting in an attempt to create a new one, which in turn caused a 500 error due to an ActiveRecord exception. When adding a deploy key that exists within another project the key would be joined to the project, but would also attempt to create a new one, which resulted in a 400 error due to the key already existing. Fixes #22741 Fixes #21754 Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
由 Robert Schilling 提交于
-
由 winniehell 提交于
-
由 Gabriel Mazetto 提交于
-
- 25 10月, 2016 7 次提交
-
-
由 Yorick Peterse 提交于
This changes ProjectCacheWorker.perform_async so it only schedules a job when no lease for the given project is present. This ensures we don't end up scheduling hundreds of jobs when they won't be executed anyway.
-
由 winniehell 提交于
-
由 Airat Shigapov 提交于
-
由 Airat Shigapov 提交于
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
- 24 10月, 2016 7 次提交
-
-
由 Robert Schilling 提交于
-
由 Luis HGO 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-
由 Robert Schilling 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Timothy Andrew 提交于
- Pass `developers_and_merge` and `developers_can_push` in `params` instead of using keyword arguments. - Refactor a slightly complex boolean check to a simple `nil?` check.
-
由 Timothy Andrew 提交于
-
由 Timothy Andrew 提交于
1. Previously, we were not removing existing access levels before creating new ones. This is not a problem for EE, but _is_ for CE, since we restrict the number of access levels in CE to 1. 2. The correct approach is: CE -> delete all access levels before updating a protected branch EE -> delete developer access levels if "developers_can_{merge,push}" is switched off 3. The dispatch is performed by checking if a "length: 1" validation is present on the access levels or not. 4. Another source of problems was that we didn't put multiple queries in a transaction. If the `destroy_all` passes, but the `update` fails, we should have a rollback. 5. Modifying the API to provide users direct access to CRUD access levels will make things a lot simpler. 6. Create `create/update` services separately for this API, which perform the necessary data translation, before calling the regular `create/update` services. The translation code was getting too large for the API endpoint itself, so this move makes sense.
-