1. 02 Jun, 2016 1 commit
  2. 20 May, 2016 1 commit
  3. 13 May, 2016 1 commit
  4. 09 May, 2016 1 commit
  5. 08 May, 2016 1 commit
    • Connor Shea's avatar
      Enable the Rubocop DeprecatedClassMethods cop · 90737768f2b7
      Connor Shea authored
      This reports uses of `File.exists?` and `Dir.exists?`, which were both
      deprecated in Ruby and will eventually be removed in favor of
      `.exist?`. Also fixes all existing uses of the deprecated methods.
      90737768f2b7
  6. 06 May, 2016 1 commit
  7. 20 Apr, 2016 1 commit
  8. 19 Apr, 2016 1 commit
  9. 12 Apr, 2016 1 commit
  10. 11 Apr, 2016 2 commits
  11. 01 Apr, 2016 1 commit
  12. 30 Mar, 2016 2 commits
  13. 29 Mar, 2016 1 commit
  14. 20 Mar, 2016 1 commit
  15. 19 Mar, 2016 2 commits
  16. 18 Mar, 2016 2 commits
  17. 16 Mar, 2016 1 commit
    • Pierre de La Morinerie's avatar
      Fix MergeRequest#source_sha when there is no diff · 91b78a0e39cf
      Pierre de La Morinerie authored
      `MergeRequest#source_sha` is expected to return the sha of the source
      branch last commit.
      
      But when a open Merge Request has no diff (e.g. all commits have already
      been merged to the target branch), `merge_request.source_sha`
      incorrectly returns `nil`.
      
      This was un-noticed before – but now that !2217 has been merged,
      it makes `Gitlab::Git::Commit.between` raise an
      "Unexpected nil argument" exception.
      
      This fixes the crash, by making sure that `source_sha` returns a
      correct result even when there is no diff available.
      91b78a0e39cf
  18. 11 Mar, 2016 2 commits
    • Baldinof's avatar
      Close merge requests when removing fork relation · 9ef06bcb0cc3
      Baldinof authored
      9ef06bcb0cc3
    • Yorick Peterse's avatar
      Use a UNION in MergeRequest.in_projects · 219c13249605
      Yorick Peterse authored
      The OR condition for source_project_id/target_project_id leads to a
      query plan that performs rather poorly on PostgreSQL due to the use of
      sub-queries. Because Rails offers no easy alternative for this
      particular problem we're forced to using a UNION for both conditions.
      The resulting query performs much faster than just using an OR.
      219c13249605
  19. 07 Mar, 2016 1 commit
  20. 05 Mar, 2016 1 commit
  21. 04 Mar, 2016 1 commit
  22. 03 Mar, 2016 2 commits
  23. 27 Feb, 2016 1 commit
  24. 19 Feb, 2016 9 commits
  25. 18 Feb, 2016 1 commit
  26. 10 Feb, 2016 1 commit