- 22 1月, 2019 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
By visiting `projects/:id` you will be redirected to project page with path in it. projects/123 => foo/bar Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 21 1月, 2019 1 次提交
-
-
由 Martin Wortschack 提交于
-
- 20 1月, 2019 1 次提交
-
-
由 Stan Hu 提交于
7075c5a1 introduced a regression in GitLab 11.7 by adding a `d-sm-block`, which caused the RSS feed icon to wrap to another line. Switching to `d-sm-flex` appears to make this appear on the same line. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56225
-
- 19 1月, 2019 1 次提交
-
-
由 Jacques Erasmus 提交于
-
- 18 1月, 2019 11 次提交
-
-
由 Oswaldo Ferreira 提交于
1. When removing projects, we can end-up leaving the +deleted repo path dirty and not successfully removing the non-deleted namespace (mv process is not atomic and can be killed without fully moving the path). 2. In order to solve that, we're adding a clean-up phase on ensure which will schedule possible staled +deleted path deletion. Note that we don't check the current state (if there is or not a repo) in order to schedule the deletion. That's intentional in order to leverage Gitlab::GitalyClient::NamespaceService#remove idempotency and ensure consistency.
-
由 Sanad Liaquat 提交于
-
由 Fabian Schneider 提交于
-
由 Sanad Liaquat 提交于
-
由 Sean McGivern 提交于
Spam checks are meant for content that could be indexed by search engines. Confidential issues aren't indexed by search engines, so we don't need to do spam checks for them. We do need to check for spam when an issue changes from confidential to public, even if nothing else changed.
-
由 Tim Zallmann 提交于
-
由 Shinya Maeda 提交于
Add spec Add changelog
-
由 Tim Zallmann 提交于
-
由 Thong Kuah 提交于
- #update_errored? method def is redundant, already defined from state machine - #update_in_progress? moved to ApplicationStatus - #ready_status becomes a constant. Previously it was extended in ee/ so maybe that was why it's a instance method
-
* dropdown position * add empty state list overflow * avoid double scrollbars in project dropdown
-
由 Brett Walker 提交于
Since the rendering of footnotes is changed, the cached html need to be updated
-
- 17 1月, 2019 10 次提交
-
-
由 Vladimir Shushlin 提交于
-
由 Nathan Friend 提交于
The expansion hover animation caused a number of layout headaches; this commit removes the animation and replaces them with hover/active/focus styles. Related issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/42769
-
由 Dmitriy Zaporozhets 提交于
For codebase consistency Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Rajat Jain 提交于
-
由 Ben 提交于
-
由 James Fargher 提交于
-
由 Jasper Maes 提交于
-
由 Tim Zallmann 提交于
-
由 Walmyr 提交于
-
由 Alejandro Rodríguez 提交于
Currently if a project is inside a nested group and a user doesn't have specific permissions for that group but does have permissions on a parent group the `GET /projects/:id` API call will return the following permissions: ```json permissions: { project_access: null, group_access: null } ``` It could also happen that the group specific permissions are of lower level than the ones the user has in parent groups. This patch makes it so that the permission returned for `group_access` is the highest from amongst the hierarchy, which is (ostensibly) the information that the API user is interested in for that field.
-
- 16 1月, 2019 15 次提交
-
-
由 Paul Slaughter 提交于
**Why?** To reduce duplicate code, it's helpful to encapsulate this behavior here.
-
由 Paul Slaughter 提交于
**Why?** This prevents erros when using actions in karma test.
-
由 Yorick Peterse 提交于
This refactors some of the logic used for protecting default branches, in particular Project#after_create_default_branch. The logic for this method is moved into a separate service class. Ideally we'd get rid of Project#after_create_default_branch entirely, but unfortunately Project#after_import depends on it. This means it has to stick around until we also refactor Project#after_import. For branch protection levels we introduce Gitlab::Access::BranchProtection, which provides a small wrapper around Integer based branch protection levels. Using this class removes the need for having to constantly refer to Gitlab::Access::PROTECTION_* constants.
-
由 Natalia Tepluhina 提交于
-
由 Yorick Peterse 提交于
This refactors the code used for checking if a user has exceeded the personal projects limit. As part of this refactor the method has been renamed from Project#check_limit to "check_personal_projects_limit", as this name makes it much more clear what the purpose of the method is. Standalone unit tests have also been added, as before we only had a single generic validation test that did not cover all cases. The old implementation of the refactored method also included a `rescue` statement. This code would only run when a project creator was not set. The error that would be added wasn't super useful, especially since there would already be errors for the creator not being present. As none of the other code in the "check_personal_projects_limit" raises, it has been removed.
-
由 Sanad Liaquat 提交于
-
由 Sanad Liaquat 提交于
-
由 Semyon Pupkov 提交于
-
由 Sanad Liaquat 提交于
-
由 Stan Hu 提交于
-
由 Mayra Cabrera 提交于
Modifies clusters form to display a disabled text field for environment scope. This changes is needed for https://gitlab.com/gitlab-org/gitlab-ce/issues/52363
-
由 Paul Slaughter 提交于
-
由 André Gama 提交于
-
由 Luke Bennett 提交于
-
由 Peter Leitzen 提交于
We introduced the feature flag `error_tracking` to test the Sentry MVC safely. After the successful test, we remove it again.
-