- 27 Apr, 2017 4 commits
-
-
Timothy Andrew authored
- We upgraded `rugged` to 0.25.1.1 in !10286 for %9.1 - Prior to this upgrade, the default sort order for commits returned by `Gitlab::Git::Repository#find_commits` was `Rugged::SORT_DATE`, which the graph relied on. - While upgrading `rugged`, the MR also changed this default to `Rugged::SORT_NONE`, which broke commit ordering in the graph. - This commit adds an option to `Gitlab::Git::Repository#find_commits` to sort by date, and changes the graph builder `Network::Graph` so it explictly requests the `:date` sort order
-
Toon Claes authored
-
Douwe Maan authored
-
Toon Claes authored
Because the post-processing of the rendered README is dependent on the context (i.e. the current user), do the post-processing when the README is being displayed.
-
- 26 Apr, 2017 4 commits
-
-
winniehell authored
-
Douglas Barbosa Alexandre authored
-
Bob Van Landuyt authored
-
Tiago Botelho authored
-
- 25 Apr, 2017 2 commits
-
-
Sean McGivern authored
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.
-
Nick Thomas authored
Swap a before_save call with a before_create/before_update pair to avoid a confict with elasticsearch-model
-
- 24 Apr, 2017 4 commits
-
-
Douwe Maan authored
-
Stan Hu authored
We see in #27387 that a call to `polymorphic_path` will cause duplicate SELECT route calls for each merge request in a milestone. This happens because calling `project.namespace.becomes(Namespace)` will instantiate a new instance of a Namespace for each merge request, which causes a N+1 query on the routes table. This change caches the state of the route by the specific class and ID, which dramatically eliminates duplicate work.
-
Toon Claes authored
And add some specs.
-
Toon Claes authored
Turn ExpirePipelineCacheService into Worker so it can fetch all the merge requests for which the pipeline runs or did run against.
-
- 21 Apr, 2017 5 commits
-
-
Grzegorz Bizon authored
-
Nick Thomas authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Nick Thomas authored
-
Stan Hu authored
Closes #31215
-
- 20 Apr, 2017 1 commit
-
-
Valery Sizov authored
-
- 19 Apr, 2017 2 commits
-
-
Adam Niedzielski authored
Closes #30964
-
James Lopez authored
-
- 18 Apr, 2017 4 commits
-
-
Robin Bobbitt authored
-
Valery Sizov authored
-
Tiago Botelho authored
-
Stan Hu authored
Before deleting a user via a SpamLog would just call `user.destroy`, which may omit other things that need to be cleaned up.
-
- 17 Apr, 2017 3 commits
-
-
Sean McGivern authored
`git log --follow` is only supported for a single path. CE doesn't currently pass multiple paths, but EE does.
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 16 Apr, 2017 1 commit
-
-
Stan Hu authored
In the case of spammers, we really want a hard delete to avoid retaining spam. Closes #31021
-
- 14 Apr, 2017 6 commits
-
-
Sean McGivern authored
-
Sean McGivern authored
-
Sean McGivern authored
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/962
-
James Lopez authored
Refactored specs and added a post deployment migration to remove the activity users table.
-
James Lopez authored
It uses a user activity table instead of a column in users. Tested with mySQL and postgreSQL
-
Sean McGivern authored
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/557
-
- 13 Apr, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 12 Apr, 2017 1 commit
-
-
Robert Speicher authored
-
- 11 Apr, 2017 2 commits
-
-
blackst0ne authored
-
Alejandro Rodríguez authored
-