BigW Consortium Gitlab

  1. 05 Apr, 2017 1 commit
  2. 27 Jan, 2017 2 commits
  3. 01 Dec, 2016 1 commit
    • Save a query on issue and MR lists · 79b5bfc1
      Sean McGivern authored
      `any?` on an AR relation performs a `SELECT COUNT`, which we don't need.
      
      1. We are very likely to have issues or MRs, so the `SELECT COUNT` is
         often unnecessary.
      2. Even where there are no items returned, the overhead of the
         `SELECT *` instead of `SELECT COUNT` is relatively small.
      
      Calling `to_a` on the relation lets us use `Enumerable#any?`, which will
      return immediately if there are objects returned.
  4. 16 Jun, 2016 2 commits
  5. 10 Jun, 2016 1 commit
  6. 26 Feb, 2016 1 commit
  7. 02 Dec, 2015 1 commit
  8. 14 Feb, 2015 1 commit
    • Upgrade to Rails 4.1.9 · 76aad9b7
      Vinnie Okada authored
      Make the following changes to deal with new behavior in Rails 4.1.2:
      
      * Use nested resources to avoid slashes in arguments to path helpers.
  9. 30 May, 2014 1 commit
  10. 29 May, 2014 2 commits
  11. 20 Feb, 2014 1 commit
  12. 24 Dec, 2013 1 commit
  13. 27 Nov, 2013 1 commit
  14. 15 Aug, 2013 1 commit
    • More specific empty state message wording · 4b91ffca
      Henry Smith authored
      I've changed all the instances of "Nothing to show here" to specifically mention
      the name of the entity of which there are none to show. This makes for a
      slightly smoother reading experience.
  15. 07 Aug, 2013 1 commit
  16. 06 Aug, 2013 1 commit
  17. 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
  18. 13 Jul, 2013 1 commit
  19. 23 Jun, 2013 1 commit
  20. 06 Apr, 2013 1 commit
  21. 14 Jan, 2013 1 commit