BigW Consortium Gitlab

  1. 19 Apr, 2016 1 commit
  2. 18 Apr, 2016 1 commit
  3. 02 Apr, 2016 1 commit
  4. 30 Mar, 2016 1 commit
  5. 04 Mar, 2016 1 commit
  6. 24 Feb, 2016 1 commit
  7. 20 Feb, 2016 4 commits
  8. 22 Jan, 2016 1 commit
  9. 21 Jan, 2016 1 commit
  10. 14 Oct, 2015 1 commit
  11. 24 Sep, 2015 1 commit
  12. 25 Aug, 2015 1 commit
  13. 20 Aug, 2015 1 commit
  14. 29 May, 2015 1 commit
  15. 15 Apr, 2015 1 commit
  16. 13 Apr, 2015 2 commits
  17. 27 Mar, 2015 1 commit
  18. 22 Mar, 2015 1 commit
  19. 11 Mar, 2015 1 commit
  20. 10 Mar, 2015 2 commits
  21. 09 Mar, 2015 3 commits
  22. 13 Feb, 2015 1 commit
  23. 05 Oct, 2014 1 commit
    • Make Spinach test names consistent · fa349012
      Ciro Santilli authored
      - do not add Feature to feature titles
      - titleize feature titles
      - put steps on the same path as .feature files
      - make feature titles match their path
  24. 01 Sep, 2014 1 commit
  25. 27 Aug, 2014 1 commit
  26. 04 Jun, 2014 1 commit
  27. 11 Feb, 2014 1 commit
  28. 24 Dec, 2013 2 commits
  29. 16 Dec, 2013 1 commit
    • Archiving old projects; archived projects aren't shown on dashboard · 37383966
      Steven Thonus authored
      features for archive projects
      abilities for archived project
      other abilities for archive projects
      
      only limit commits and merges for archived projects
      
      ability changed to prohibited actions on archived projects
      
      added spec and feature tests for archive projects
      
      changed search bar not to include archived projects
  30. 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
  31. 19 Jun, 2013 1 commit
  32. 06 Jun, 2013 1 commit