- 24 7月, 2017 1 次提交
-
-
由 Jarka Kadlecova 提交于
-
- 14 7月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 08 7月, 2017 2 次提交
-
-
由 Stan Hu 提交于
Identified via `ENABLE_BULLET=1 bundle exec rspec spec/requests/api/merge_requests_spec.rb:34` Improves speed of #34159
-
由 James Lopez 提交于
-
- 07 7月, 2017 2 次提交
-
-
由 Sean McGivern 提交于
For merge requests created after 9.4, we have a `merge_request_diff_commits` table we can get all the SHAs from very quickly. We just need to exclude these when we load from the legacy format, by ignoring diffs with no serialised commits. Once these have been migrated in the background, every MR will see this improvement.
-
由 Sean McGivern 提交于
This is an ID-less table with just three columns: an association to the merge request diff the commit belongs to, the relative order of the commit within the merge request diff, and the commit SHA itself. Previously we stored much more information about the commits, so that we could display them even when they were deleted from the repo. Since 8.0, we ensure that those commits are kept around for as long as the target repo itself is, so we don't need to duplicate that data in the database.
-
- 06 7月, 2017 3 次提交
-
-
由 Yorick Peterse 提交于
This cop has been renamed to ActiveRecordSerialize to match the way "ActiveRecord" is usually written.
-
由 Yorick Peterse 提交于
This is allowed for existing instances so we don't end up 76 offenses right away, but for new code one should _only_ use this if they _have_ to remove non database data. Even then it's usually better to do this in a service class as this gives you more control over how to remove the data (e.g. in bulk).
-
由 Yorick Peterse 提交于
This removes the need for relying on Rails' "dependent" option for data removal, which is _incredibly_ slow (even when using :delete_all) when deleting large amounts of data. This also ensures data consistency is enforced on DB level and not on application level (something Rails is really bad at). This commit also includes various migrations to add foreign keys to tables that eventually point to "projects" to ensure no rows get orphaned upon removing a project.
-
- 26 6月, 2017 1 次提交
-
-
由 Adam Niedzielski 提交于
Closes #34052
-
- 21 6月, 2017 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Toon Claes 提交于
To make it simpler to assign users to an Issuable, make MergeRequest support the attribute `assignee_ids`.
-
- 16 6月, 2017 1 次提交
-
-
由 Felipe Artur 提交于
-
- 15 6月, 2017 1 次提交
-
-
由 Eric Eastwood 提交于
Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/27070 Deprecate "chat commands" in favor of "slash commands" We looked for things like: - `slash commmand` - `slash_command` - `slash-command` - `SlashCommand`
-
- 01 6月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 31 5月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
This Cop blacklists the use of ActiveRecord's "serialize" method, except for cases where we already use this.
-
- 30 5月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 24 5月, 2017 2 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 19 5月, 2017 1 次提交
-
-
由 Douwe Maan 提交于
-
- 13 5月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
I don't know why this happens exactly, but given an upstream and fork repository from a customer, both of which required GC, resolving conflicts would corrupt the fork so badly that it couldn't be cloned. This isn't a perfect fix for that case, because the MR may still need to be merged manually, but it does ensure that the repository is at least usable. My best guess is that when we generate the index for the conflict resolution (which we previously did in the target project), we obtain a reference to an OID that doesn't exist in the source, even though we already fetch the refs from the target into the source. Explicitly setting the source project as the place to get the merge index from seems to prevent repository corruption in this way.
-
- 12 5月, 2017 1 次提交
-
-
由 Valery Sizov 提交于
-
- 09 5月, 2017 1 次提交
-
-
由 Fatih Acet 提交于
-
- 08 5月, 2017 1 次提交
-
-
由 Felipe Artur 提交于
-
- 04 5月, 2017 2 次提交
-
-
由 Valery Sizov 提交于
-
由 Douwe Maan 提交于
-
- 27 4月, 2017 1 次提交
-
-
由 mhasbini 提交于
-
- 25 4月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
The problem is that we often go via a diff object constructed from the diffs stored in the DB. Those diffs, by definition, don't overflow, so we don't have access to the 'correct' `real_size` - that is stored on the MR diff object iself.
-
- 11 4月, 2017 1 次提交
-
-
由 Robert Speicher 提交于
-
- 09 4月, 2017 3 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 06 4月, 2017 3 次提交
-
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
由 Douwe Maan 提交于
-
- 04 4月, 2017 2 次提交
-
-
-
由 James Edwards-Jones 提交于
-
- 22 3月, 2017 1 次提交
-
-
由 mhasbini 提交于
-
- 21 3月, 2017 1 次提交
-
-
由 Sean McGivern 提交于
This reverts merge request !10076
-
- 20 3月, 2017 1 次提交
-
-
由 Jarka Kadlecova 提交于
-