- 15 Jan, 2018 1 commit
-
-
Ahmad Sherif authored
Closes gitaly#915
-
- 12 Jan, 2018 2 commits
-
-
Hiroyuki Sato authored
-
Sean McGivern authored
If we search for notes before the MR was merged, we have to load every commit that was ever part of the MR, or mentioned in a push. In extreme cases, this can be tens of thousands of commits to load, but we know they can't revert the merge commit, because they are from before the MR was merged. In the (rare) case that we don't have a `merged_at` value for the MR, we can still search all notes.
-
- 04 Jan, 2018 1 commit
-
-
Jacob Vosmaer authored
-
- 19 Dec, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
Uses `list_commits_by_oid` on the CommitService, to request the needed commits for pipelines. These commits are needed to display the user that created the commit and the commit title. This includes fixes for tests failing that depended on the commit being `nil`. However, now these are batch loaded, this doesn't happen anymore and the commits are an instance of BatchLoader.
-
- 13 Dec, 2017 1 commit
-
-
Jacopo authored
Allows ordering in GET api/v4/projects/:project_id/repository/contributors through `order_by` and `sort` params. The available `order_by` options are: name|email|commits. The available `sort` options are: asc|desc.
-
- 07 Dec, 2017 1 commit
-
-
micael.bergeron authored
-
- 23 Nov, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 21 Nov, 2017 1 commit
-
-
Zeger-Jan van de Weg authored
After installing a new gem, batch-loader, a construct can be used to queue data to be fetched in bulk. The gem was also introduced in both gitlab-org/gitlab-ce!14680 and gitlab-org/gitlab-ce!14846, but those mrs are not merged yet. For the generation of diffs, both the old blob and the new blob need to be loaded. This for every file in the diff, too. Now we collect all these so we do 1 fetch. Three `.allow_n_plus_1_calls` have been removed, which I expect to be valid, but this needs to be confirmed by a full CI run. Possibly closes: - https://gitlab.com/gitlab-org/gitlab-ce/issues/37445 - https://gitlab.com/gitlab-org/gitlab-ce/issues/37599 - https://gitlab.com/gitlab-org/gitlab-ce/issues/37431
-
- 16 Nov, 2017 2 commits
-
-
Yorick Peterse authored
This adds an optimised way of getting the latest pipeline status for a list of Commit objects (or just a single one).
-
micael.bergeron authored
-
- 15 Nov, 2017 2 commits
-
-
micael.bergeron authored
-
micael.bergeron authored
-
- 25 Sep, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 06 Sep, 2017 1 commit
-
-
Tiago Botelho authored
-
- 05 Sep, 2017 1 commit
-
-
Alexis Reigel authored
we need the commit object for the updated verification that also checks the committer's email to match the gpg key and user's emails.
-
- 21 Aug, 2017 2 commits
-
-
Saverio Miroddi authored
-
Saverio Miroddi authored
Also improved the UT for better documenting this change.
-
- 17 Aug, 2017 1 commit
-
-
Saverio Miroddi authored
The list of commits must be generated from the merge request, not from a diff of the branches.
-
- 16 Aug, 2017 1 commit
-
-
Douwe Maan authored
-
- 15 Aug, 2017 3 commits
-
-
Saverio Miroddi authored
-
Saverio Miroddi authored
Follow the `cherry pick -x` format for the first line, and the interactive rebase format for the commits in the merge, in case of merge commit
-
Saverio Miroddi authored
This also fixes the inconsistency between non/merge commits in the number of newlines introduced.
-
- 14 Aug, 2017 1 commit
-
-
Robert Speicher authored
An upcoming update to rubocop-gitlab-security added additional violations.
-
- 10 Aug, 2017 1 commit
-
-
Saverio Miroddi authored
Store the original commit in the commit message. In case of merge commit, the commits added to the start branch are also listed.
-
- 08 Aug, 2017 2 commits
-
-
Alejandro Rodríguez authored
This helps keep the abstraction layers simpler, and also keep the interface of those methods consistent, in case of implementation changes.
-
Alejandro Rodríguez authored
-
- 27 Jul, 2017 8 commits
-
-
Alexis Reigel authored
-
Alexis Reigel authored
as we write the cache in the gpg commit class already the read should also happen there. This also removes all logic from the main commit class, which just proxies the call to the Gpg::Commit now.
-
Alexis Reigel authored
-
Alexis Reigel authored
we store the result of the gpg commit verification in the db because the gpg verification is an expensive operation.
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Alexis Reigel authored
-
Kevin O'Connor authored
-
- 18 Jul, 2017 3 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Andrew Newdigate authored
-
- 17 Jul, 2017 1 commit
-
-
Lin Jen-Shin authored
We also try to use instance variable to cache the result if RequestStore is not available, so we could keep the same logic, using the same cache key. Also introduce a way to specify method specific cache key
-