- 01 9月, 2017 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 31 8月, 2017 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 30 8月, 2017 2 次提交
-
-
由 Lin Jen-Shin 提交于
-
由 Hiroyuki Sato 提交于
-
- 29 8月, 2017 17 次提交
-
-
由 Lin Jen-Shin 提交于
So it's more clear what could happen. Also add more tests about the behaviour.
-
由 Lin Jen-Shin 提交于
-
由 Lin Jen-Shin 提交于
-
由 Maxim Rydkin 提交于
-
由 Maxim Rydkin 提交于
-
由 Maxim Rydkin 提交于
-
由 Maxim Rydkin 提交于
-
由 Maxim Rydkin 提交于
-
由 Maxim Rydkin 提交于
-
由 Maxim Rydkin 提交于
-
由 Maxim Rydkin 提交于
-
由 Maxim Rydkin 提交于
-
由 Hiroyuki Sato 提交于
-
由 Oswaldo Ferreira 提交于
-
由 Oswaldo Ferreira 提交于
-
由 Oswaldo Ferreira 提交于
-
由 Oswaldo Ferreira 提交于
Our state machine shall have enough knowledge to not allow states other than locked from transitioning to opened (e.g. MergeRequest#unlock_mr).
-
- 28 8月, 2017 1 次提交
-
-
由 Lin Jen-Shin 提交于
-
- 26 8月, 2017 1 次提交
-
-
由 James Edwards-Jones 提交于
-
- 25 8月, 2017 4 次提交
-
-
由 Nick Thomas 提交于
If the project is in a group, the `group.refresh_members_authorized_projects` is made non-blocking, and we call `current_user.refresh_authorized_projects` directly. Projects in a personal namespace are more difficult. Rather than passing the `blocking:` parameter through the entire `add_master` chain, have the `AuthorizedProjectsWorker` automatically inline authorizations for three IDs or less. Since the maximum number of IDs in this path is 2, that has the same effect.
-
由 Lin Jen-Shin 提交于
So that whenever we want to reserve more, we're aware, and don't mess it up.
-
由 Lin Jen-Shin 提交于
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/13766 * Rename AfterImportService * Use constants * Move Git operations to Gitlab::Git::Repository * Use Regexp.union
-
由 Hiroyuki Sato 提交于
-
- 24 8月, 2017 5 次提交
-
-
由 Jacob Vosmaer 提交于
-
由 Lin Jen-Shin 提交于
-
由 Andrew Newdigate 提交于
-
由 Mehdi Lahmam 提交于
Closes #35994
-
由 haseeb 提交于
-
- 23 8月, 2017 7 次提交
-
-
由 Lin Jen-Shin 提交于
Because we don't need them, and they would slow down the repository, keeping unneeded objects as well. We could also consider doing this in regular housekeeping.
-
由 Yorick Peterse 提交于
Every project page displays a navigation menu that in turn displays the number of open issues and merge requests. This means that for every project page we run two COUNT(*) queries, each taking up roughly 30 milliseconds on GitLab.com. By caching these numbers and refreshing them whenever necessary we can reduce loading times of all these pages by up to roughly 60 milliseconds. The number of open issues does not include confidential issues. This is a trade-off to keep the code simple and to ensure refreshing the data only needs 2 COUNT(*) queries instead of 3. A downside is that if a project only has 5 confidential issues the counter will be set to 0. Because we now have 3 similar counting service classes the code previously used in Projects::ForksCountService has mostly been moved to Projects::CountService, which in turn is reused by the various service classes. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36622
-
由 Zeger-Jan van de Weg 提交于
It was missing and expected it wouldn't hurt anyone
-
由 Jacob Vosmaer 提交于
-
由 Jacob Vosmaer 提交于
-
由 Grzegorz Bizon 提交于
-
由 Yorick Peterse 提交于
This changes the style of push events that remove tags or branches so they don't display the commit details. This prevents displaying commit details such as: 000000 . --broken encoding Instead we now simply display the header such as: Administrator deleted branch example-branch This is displayed in the same style as events for newly created branches/tags. This commit also ensures that if no commit message is present we simply don't display anything, instead of "--broken encoding". Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36685 Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36722
-
- 22 8月, 2017 1 次提交
-
-
由 Grzegorz Bizon 提交于
-