- 04 Oct, 2017 2 commits
-
- 03 Oct, 2017 10 commits
-
-
Douwe Maan authored
-
Kushal Pandya authored
-
Greg Stark authored
-
Winnie Hellmann authored
-
Greg Stark authored
-
Alessio Caiazza authored
-
Jarka Kadlecova authored
-
Mark Fletcher authored
-
Alessio Caiazza authored
- 02 Oct, 2017 10 commits
-
-
Douglas Barbosa Alexandre authored
-
Douwe Maan authored
-
Stan Hu authored
Because of a change in GitLab 9.5.4 to prevent users from assuming control of a repository already on disk, the import task broke. Imports would fail with the message, "There is already a repository with that name on disk". This change skips the validation when the import is done from the command-line. Closes #37682
-
Nick Thomas authored
-
Stan Hu authored
The Redcarpet library is not thread-safe as described in https://github.com/vmg/redcarpet/issues/570. Since we instantiate the Redcarpet renderer in a class variable, multiple Sidekiq threads can access the work buffer and corrupt the state. We work around this issue by memoizing the renderer on a thread basis. Closes #36637
-
Yorick Peterse authored
In this particular case the use of UNION ALL leads to a better query plan compared to using 1 big query that uses an OR statement to combine different data sources. See https://gitlab.com/gitlab-org/gitlab-ce/issues/38508 for more information.
-
Guilherme Vieira authored
-
Nick Thomas authored
-
Mark Fletcher authored
-
Stan Hu authored
`Repository#has_visible_content?` used to rely on the cached count of local branches, but since it is now an independently cached value it needs to be invalidated on its own. Closes #38646
-
- 01 Oct, 2017 1 commit
-
-
robdel12 authored
-
- 29 Sep, 2017 15 commits
-
-
Stan Hu authored
To restore all refs from a bundle, we need to use the --mirror option to ensure that all refs are properly restored. Without this, refs such as `refs/merge-requests/X` and `refs/keep-around/Y` would be omitted, which exposed a bug as described in https://gitlab.com/gitlab-org/gitlab-ce/issues/38319#note_41648608. Closes #38352
-
David Turner authored
When calling pre-receive, post-receive, and update hooks, add the GitLab username as the GL_USERNAME environment variable. This patch only handles cases where pushes are over http, or via the web interface. Later, we will address the ssh case.
-
Tim Bishop authored
In line with other changes in GitLab, make email address validation properly case insensitive. The email address in the commit may be in any case, so it needs downcasing to match the address stored in GitLab for the user. Without this change the comparison fails and commits are not marked as verified. See #37009.
-
Jose Ivan Vargas authored
[ci skip]
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Valery Sizov authored
-
Phil Hughes authored
Closes #38411
-
kushalpandya authored
-
Sean McGivern authored
All of these were in past releases, so missed their chance to be included in the main changelog :-(
-
Filipa Lacerda authored
-
Lin Jen-Shin (godfat) authored
-
Sean McGivern authored
The first attempt didn't migrate all rows on GitLab.com, due to a couple of issues: 1. Some rows in merge_request_diffs had truly huge numbers of commits and diffs serialised - one in particular had 26,000 commits! 2. The jobs were sometimes on Sidekiq hosts with frequent OOM errors, leading to the job being lost. The previous commit adds more logging, and a more robust insertion method. This commit reschedules the jobs, with a generous pause between each.
-
Phil Hughes authored
Previously the fork button was disabled for all users if they have exceeded their project limit. This fixes that by changing the check to see if the user can fork to a group instead of their own namespace. This behaviour is already possible by visiting the new fork page directly, so this just fixes the button being disabled. Closes #38462
-
Phil Hughes authored
Previously the merge request widget would use the `updated_at` date as the tooltip text for both closed & merged states. This is incorrect as the `updated_at` date is actually changed when a user updates merge request through commenting, description changes or anything else. The widget states for merged & closed events now use their own event object which holds their own `updated_at` date string. Also this text has been correctly formatted through our date utilities to correctly display the right timezone data in a user friendly way. Closes #38545
-
Phil Hughes authored
-
- 28 Sep, 2017 2 commits
-
-
Annabel Dunstone Gray authored
-
Markus Koller authored
-