- 07 Jul, 2017 2 commits
-
-
Jacob Vosmaer authored
-
Ahmad Sherif authored
Closes gitaly#355
-
- 05 Jul, 2017 3 commits
-
-
Tiago Botelho authored
-
Tiago Botelho authored
-
Jacob Vosmaer authored
-
- 04 Jul, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 30 Jun, 2017 2 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 29 Jun, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 28 Jun, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 27 Jun, 2017 3 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
- 22 Jun, 2017 1 commit
-
-
Ahmad Sherif authored
-
- 21 Jun, 2017 2 commits
-
-
Ahmad Sherif authored
-
Grzegorz Bizon authored
-
- 16 Jun, 2017 2 commits
-
-
David Turner authored
Submodules have a name in the configuration, but this name is simply the path at which the submodule was initially checked in (by default -- the name is totally arbitrary). If a submodule is moved, it retains its original name, but its path changes. Since we discover submodules inside trees, we have their path but not necessarily their name. Make the submodules() function return the submodule hash indexed by path rather than name, so that renamed submodules can be looked up. Signed-off-by: David Turner <novalis@novalis.org>
-
Sean McGivern authored
This adds an ID-less table containing one row per file, per merge request diff. It has a column for each attribute on Gitlab::Git::Diff that is serialised currently, with the advantage that we can easily query the attributes of this new table. It does not migrate existing data, so we have fallback code when the legacy st_diffs column is present instead. For a merge request diff to be valid, it should have at most one of: * Rows in this new table, with the correct merge_request_diff_id. * A non-NULL st_diffs column. It may have neither, if the diff is empty.
-
- 14 Jun, 2017 1 commit
-
-
Robert Speicher authored
-
- 08 Jun, 2017 1 commit
-
-
Douwe Maan authored
-
- 06 Jun, 2017 1 commit
-
-
Douwe Maan authored
-
- 02 Jun, 2017 2 commits
-
-
Sean McGivern authored
This is controlled with the feature flag gitlab_git_diff_size_limit_increase. Both of these limits were basically picked arbitrarily in the first place; disabling the feature flag reverts to the old limits.
-
Ahmad Sherif authored
-
- 01 Jun, 2017 1 commit
-
-
Bob Van Landuyt authored
-
- 31 May, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 30 May, 2017 2 commits
-
-
Douwe Maan authored
-
Bob Van Landuyt authored
-
- 29 May, 2017 1 commit
-
-
Douwe Maan authored
-
- 23 May, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 17 May, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 16 May, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 10 May, 2017 2 commits
-
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 04 May, 2017 1 commit
-
-
Timothy Andrew authored
- Previously, we sorted commits by date, which seemed to work okay. - The one edge case where this failed was when multiple commits have the same commit date (for example: when a range of commits are cherry picked with a single command, they all have the same commit date [and different author dates]). - Commits with the same commit date would be sorted arbitrarily, and usually break the network graph. - This commit solves the problem by both sorting by date, and by sorting topographically (parents aren't displayed until all their children are displayed) - Include review comments from @adamniedzielski A more detailed explanation is present here: https://gitlab.com/gitlab-org/gitlab-ce/issues/30973#note_28706230
-
- 02 May, 2017 1 commit
-
-
Alejandro Rodríguez authored
-
- 01 May, 2017 1 commit
-
-
Robert Speicher authored
-
- 28 Apr, 2017 1 commit
-
-
Kim "BKC" Carlbäcker authored
-
- 27 Apr, 2017 1 commit
-
-
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
-
- 20 Apr, 2017 1 commit
-
-
James Lopez authored
-