BigW Consortium Gitlab

  1. 17 Feb, 2016 1 commit
  2. 15 Feb, 2016 1 commit
    • Fix the "x of y" displayed at the top of Issuables' sidebar · 54613b6a
      Rémy Coutable authored
      1. We now display the index of the current issuable among all its project's
      issuables, of the same type and with the same state.
      2. Also, refactored a bit the Issuable helpers into a new IssuablesHelper
      module.
      3. Added acceptance specs for the sidebar counter.
  3. 22 Jan, 2016 2 commits
  4. 21 Jan, 2016 1 commit
  5. 19 Jan, 2016 2 commits
  6. 11 Dec, 2015 1 commit
  7. 09 Dec, 2015 2 commits
  8. 10 Nov, 2015 1 commit
  9. 23 Oct, 2015 1 commit
  10. 30 Sep, 2015 1 commit
  11. 26 Jun, 2015 1 commit
  12. 23 Jun, 2015 1 commit
  13. 19 Jun, 2015 1 commit
  14. 29 May, 2015 1 commit
  15. 25 May, 2015 1 commit
  16. 06 May, 2015 1 commit
  17. 26 Mar, 2015 1 commit
  18. 16 Mar, 2015 1 commit
  19. 12 Mar, 2015 1 commit
    • Implement merge requests search · 80b2f3fb
      Dmitriy Zaporozhets authored
      It is same search like we have at issues page. It allows to quickly
      filter merge requests based on title or desription. I copy-pasted some
      js code from Issues.js. In future search (filtering) logic should be
      refactoed into one class for merge requests and issues
  20. 18 Oct, 2014 2 commits
  21. 16 Oct, 2014 1 commit
  22. 07 Oct, 2014 1 commit
  23. 06 Oct, 2014 2 commits
  24. 12 Sep, 2014 1 commit
  25. 14 Aug, 2014 1 commit
  26. 31 Jul, 2014 1 commit
  27. 03 Mar, 2014 1 commit
  28. 22 Feb, 2014 1 commit
  29. 18 Feb, 2014 1 commit
  30. 11 Feb, 2014 1 commit
  31. 23 Jan, 2014 1 commit
  32. 14 Jan, 2014 1 commit
  33. 18 Jul, 2013 1 commit
    • 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
  34. 28 Feb, 2013 2 commits