1. 11 Aug, 2017 1 commit
  2. 09 Aug, 2017 1 commit
  3. 08 Aug, 2017 2 commits
  4. 04 Aug, 2017 1 commit
  5. 03 Aug, 2017 2 commits
  6. 02 Aug, 2017 1 commit
  7. 01 Aug, 2017 1 commit
  8. 27 Jul, 2017 3 commits
  9. 18 Jul, 2017 1 commit
  10. 14 Jul, 2017 2 commits
  11. 13 Jul, 2017 1 commit
  12. 07 Jul, 2017 1 commit
  13. 05 Jul, 2017 1 commit
  14. 04 Jul, 2017 1 commit
  15. 30 Jun, 2017 2 commits
  16. 28 Jun, 2017 1 commit
  17. 27 Jun, 2017 2 commits
  18. 21 Jun, 2017 1 commit
  19. 16 Jun, 2017 1 commit
    • David Turner's avatar
      repository: index submodules by path · b30c16aa
      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: default avatarDavid Turner <novalis@novalis.org>
      b30c16aa
  20. 14 Jun, 2017 1 commit
  21. 08 Jun, 2017 1 commit
  22. 01 Jun, 2017 1 commit
  23. 30 May, 2017 1 commit
  24. 18 May, 2017 1 commit
  25. 16 May, 2017 1 commit
  26. 04 May, 2017 1 commit
    • Timothy Andrew's avatar
      Sort the network graph both by commit date and topographically. · b44eaf8e
      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
      b44eaf8e
  27. 02 May, 2017 1 commit
  28. 28 Apr, 2017 1 commit
  29. 27 Apr, 2017 1 commit
    • Timothy Andrew's avatar
      Fix ordering of commits in the network graph. · a7e67604
      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
      a7e67604
  30. 11 Apr, 2017 1 commit
  31. 10 Apr, 2017 1 commit
  32. 04 Apr, 2017 1 commit
  33. 30 Mar, 2017 1 commit