- Mar 20, 2020
-
-
GitLab Bot authored
-
- Mar 07, 2020
-
-
GitLab Bot authored
-
- Jan 29, 2020
-
-
GitLab Bot authored
-
- Jan 14, 2020
-
-
GitLab Bot authored
-
- Dec 11, 2019
-
-
GitLab Bot authored
-
- Dec 04, 2019
-
-
GitLab Bot authored
-
- Nov 27, 2019
-
-
GitLab Bot authored
-
- Nov 20, 2019
-
-
GitLab Bot authored
-
- Nov 15, 2019
-
-
GitLab Bot authored
-
- Nov 14, 2019
-
-
GitLab Bot authored
-
- Oct 18, 2019
-
-
GitLab Bot authored
-
- Oct 17, 2019
-
-
GitLab Bot authored
-
- Oct 10, 2019
-
-
GitLab Bot authored
-
- Oct 09, 2019
-
-
GitLab Bot authored
-
- Sep 18, 2019
-
-
GitLab Bot authored
-
- Sep 04, 2019
-
-
pshutsin authored
Improve diff lines count efficiency
-
- Aug 29, 2019
-
-
dineshpanda authored
-
- Aug 06, 2019
-
-
pshutsin authored
-
- May 06, 2019
-
-
Nick Thomas authored
-
- Apr 30, 2019
-
-
Heinrich Lee Yu authored
Prepares us for upgrade to Rails 5.2
-
- Apr 15, 2019
-
-
Kamil Trzcińśki authored
The `#reload` makes to load all objects into memory, and the main purpose of `#reload` is to drop the association cache. The `#reset` seems to solve exactly that case.
-
- Mar 28, 2019
-
-
Nick Thomas authored
-
- Mar 27, 2019
-
-
Nick Thomas authored
Since external diffs are likely to be a bit slower than in-database ones, add a mode that makes diffs external after they've been obsoleted by events. This should strike a balance between performance and disk space. A background cron drives the majority of migrations, since diffs become outdated through user actions.
-
- Mar 14, 2019
-
-
Stan Hu authored
If a diff happened to include a single null byte anywhere, insertion into the database would fail with an Error 500 since the column is text and not a byte array. To fix this, we mark the diff as binary if we detect a single null byte and Base64-encode it. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57710
-
- Mar 13, 2019
-
-
Nick Thomas authored
-
- Mar 04, 2019
-
-
Francisco Javier López authored
-
- Feb 14, 2019
-
-
Nick Thomas authored
-
- Feb 05, 2019
-
-
Nick Thomas authored
-
- Nov 26, 2018
-
-
Jasper Maes authored
-
- Nov 12, 2018
-
-
Stan Hu authored
When a branch is deleted, the push commit IDs is an empty array. The previous change would attempt to call `[].exists?`, which is invalid. Fix this by returning `MergeRequestDiffCommit.none` instead. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/53853
-
- Nov 07, 2018
-
-
Mark Chao authored
Fetch database columns directly if available
-
- Nov 02, 2018
-
-
Stan Hu authored
Previously for a given merge request, we would: 1. Create the array of commit SHAs involved in the push (A) 2. Request all merge request commits and map the SHA (B) 3. Reload the diff if there were any common commits between A and B We can avoid additional database querying and overhead by checking with the database whether the merge request contains any of the commit SHAs. Relates to https://gitlab.com/gitlab-org/gitlab-ce/issues/53213
-
- Sep 11, 2018
-
-
Yorick Peterse authored
This whitelists all existing offenses for the various CodeReuse cops, of which most are triggered by the CodeReuse/ActiveRecord cop.
-
- Aug 27, 2018
-
-
Michael Kozono authored
-
- Aug 01, 2018
-
-
Oswaldo Ferreir authored
-
- Jul 26, 2018
-
-
gfyoung authored
Partially addresses #47424.
-
- Jul 18, 2018
-
-
Oswaldo Ferreir authored
-
- Jun 24, 2018
-
-
Oswaldo Ferreir authored
-
- Apr 25, 2018
-
-
Jan Provaznik authored
* processes any pending records which are not migrated yet * bumps import_export version because of new commits_count attribute * removes commits_count fallback method
-
- Mar 08, 2018
-
-
Jan Provaznik authored
This reverts commit 0b7d1085.
-