1. 07 Dec, 2017 1 commit
  2. 27 Jul, 2017 1 commit
  3. 05 Jul, 2017 1 commit
  4. 29 Jun, 2017 1 commit
  5. 22 Jun, 2017 1 commit
  6. 03 Jun, 2017 1 commit
  7. 06 Mar, 2017 1 commit
  8. 24 Jan, 2017 1 commit
  9. 29 Dec, 2016 2 commits
  10. 04 Nov, 2016 1 commit
  11. 24 Oct, 2016 1 commit
  12. 16 Jun, 2016 2 commits
  13. 08 Jun, 2016 1 commit
  14. 03 Jun, 2016 2 commits
  15. 19 May, 2016 1 commit
    • Sean McGivern's avatar
      Chunk commits by date in lists · 37415e58
      Sean McGivern authored
      It's possible to construct a commit graph where the output of `git log`
      isn't in timestamp order. Grouping the commits in the list by date then
      gives dramatically wrong results. Instead, go for the more pragmatic
      approach: use the commits in the order they're given, and just show the
      date line each time the date changes. This means that the same date
      header can show up multiple times, but at least the ordering is
      preserved.
      37415e58
  16. 11 May, 2016 1 commit
    • Sean McGivern's avatar
      Group commits by date in server timezone · d9574a7b
      Sean McGivern authored
      `Time#to_date` just takes the (timezone-less) year, date, and month, and
      creates a new date from that. Because the commits in the list are
      grouped by date, rather than chunked when the date changes, a commit can
      be shown in the wrong order if its CommitDate has a timezone-less date
      that's different to other commits around it.
      
      Convert all CommitDates to the server timezone before grouping, as that
      will at least produce consistent results. Users can still see a
      timestamp on the commit that doesn't match the date it's grouped under,
      because the timestamp shown uses the user's local timezone, and the
      grouping uses the server's timezone, but that was an issue anyway.
      d9574a7b
  17. 25 Mar, 2016 1 commit
  18. 09 Mar, 2016 1 commit
  19. 07 Mar, 2016 1 commit
  20. 04 Mar, 2016 2 commits
  21. 07 Jan, 2016 1 commit
  22. 20 Feb, 2015 1 commit
  23. 17 Jan, 2015 1 commit
  24. 07 Jan, 2015 1 commit
  25. 03 Oct, 2014 1 commit
  26. 10 Jun, 2014 1 commit
  27. 30 Dec, 2013 1 commit
  28. 10 Sep, 2013 1 commit
  29. 09 Sep, 2013 1 commit
  30. 08 Aug, 2013 1 commit
  31. 18 Jul, 2013 2 commits
    • Izaak Alpert's avatar
      Style changes from review with @randx · d9959427
      Izaak Alpert authored
      -Some changes around calling origional methods for !for_fork? merge requests. Other changes to follow
      
      Change-Id: I009c716ce2475b9efa3fd07aee9215fca7a1c150
      d9959427
    • Izaak Alpert's avatar
      Merge Request on forked projects · 3d7194f0
      Izaak Alpert authored
      The good:
      
       - You can do a merge request for a forked commit and it will merge properly (i.e. it does work).
       - Push events take into account merge requests on forked projects
       - Tests around merge_actions now present, spinach, and other rspec tests
       - Satellites now clean themselves up rather then recreate
      
      The questionable:
      
       - Events only know about target projects
       - Project's merge requests only hold on to MR's where they are the target
       - All operations performed in the satellite
      
      The bad:
      
        -  Duplication between project's repositories and satellites (e.g. commits_between)
      
      (for reference: http://feedback.gitlab.com/forums/176466-general/suggestions/3456722-merge-requests-between-projects-repos)
      
      Fixes:
      
      Make test repos/satellites only create when needed
      -Spinach/Rspec now only initialize test directory, and setup stubs (things that are relatively cheap)
      -project_with_code, source_project_with_code, and target_project_with_code now create/destroy their repos individually
      -fixed remote removal
      -How to merge renders properly
      -Update emails to show project/branches
      -Edit MR doesn't set target branch
      -Fix some failures on editing/creating merge requests, added a test
      -Added back a test around merge request observer
      -Clean up project_transfer_spec, Remove duplicate enable/disable observers
      -Ensure satellite lock files are cleaned up, Attempted to add some testing around these as well
      -Signifant speed ups for tests
      -Update formatting ordering in notes_on_merge_requests
      -Remove wiki schema update
      Fixes for search/search results
      -Search results was using by_project for a list of projects, updated this to use in_projects
      -updated search results to reference the correct (target) project
      -udpated search results to print both sides of the merge request
      
      Change-Id: I19407990a0950945cc95d62089cbcc6262dab1a8
      3d7194f0
  32. 13 Jul, 2013 1 commit
  33. 23 Jun, 2013 1 commit
  34. 03 Apr, 2013 1 commit
  35. 25 Jan, 2013 1 commit