1. 15 Dec, 2017 1 commit
  2. 07 Dec, 2017 1 commit
  3. 05 Dec, 2017 2 commits
  4. 16 Nov, 2017 1 commit
  5. 08 Nov, 2017 1 commit
  6. 07 Nov, 2017 1 commit
  7. 03 Nov, 2017 1 commit
  8. 02 Nov, 2017 1 commit
  9. 31 Oct, 2017 1 commit
  10. 19 Sep, 2017 1 commit
  11. 06 Sep, 2017 2 commits
  12. 05 Sep, 2017 1 commit
    • Yorick Peterse's avatar
      Re-use issue/MR counts for the pagination system · 42062a45
      Yorick Peterse authored
      This changes the issue and MR index pages so the pagination system
      re-uses the output of the COUNT(*) query used to calculate the number of
      rows per state (opened, closed, etc). This removes the need for an
      additional COUNT(*) on both pages.
      42062a45
  13. 28 Aug, 2017 2 commits
  14. 15 Aug, 2017 1 commit
  15. 07 Aug, 2017 1 commit
  16. 26 Jul, 2017 1 commit
  17. 14 Jul, 2017 1 commit
  18. 05 Jul, 2017 1 commit
  19. 29 Jun, 2017 1 commit
  20. 21 Jun, 2017 3 commits
  21. 23 May, 2017 2 commits
  22. 19 May, 2017 1 commit
  23. 15 May, 2017 1 commit
  24. 12 May, 2017 1 commit
    • Sean McGivern's avatar
      Fix conflict resolution from corrupted upstream · ad2bfeb8
      Sean McGivern authored
      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.
      ad2bfeb8
  25. 09 May, 2017 2 commits
  26. 03 May, 2017 1 commit
  27. 12 Apr, 2017 1 commit
  28. 11 Apr, 2017 1 commit
  29. 10 Apr, 2017 1 commit
  30. 08 Apr, 2017 3 commits
  31. 06 Apr, 2017 1 commit