BigW Consortium Gitlab

  1. 16 Nov, 2015 1 commit
  2. 12 Nov, 2015 1 commit
    • Avoid render edit_form in each notes. · 19740871
      Jason Lee authored
      Use RJS to render edit note feature.
      
      Before:
      
      ```
      Rendered projects/notes/_note.html.haml (27.9ms)
      Rendered projects/_zen.html.haml (0.3ms)
      Rendered projects/notes/_hints.html.haml (0.7ms)
      Rendered projects/_md_preview.html.haml (3.9ms)
      Rendered projects/notes/_edit_form.html.haml (6.9ms)
      Rendered projects/notes/_note.html.haml (17.7ms)
      Rendered projects/_zen.html.haml (0.3ms)
      Rendered projects/notes/_hints.html.haml (0.6ms)
      Rendered projects/_md_preview.html.haml (3.4ms)
      Rendered projects/notes/_edit_form.html.haml (7.0ms)
      ```
      
      After:
      
      ```
      Rendered projects/notes/_note.html.haml (13.8ms)
      Rendered projects/notes/_note.html.haml (7.1ms)
      Rendered projects/notes/_note.html.haml (9.5ms)
      Rendered projects/notes/_note.html.haml (8.5ms)
      ```
      
      This change reduce at least 6ms * N ('N' - number of notes).
  3. 07 Jul, 2015 1 commit
  4. 26 Jun, 2015 1 commit
  5. 22 Jun, 2015 1 commit
  6. 13 Jun, 2015 2 commits
  7. 17 Feb, 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. 12 Feb, 2015 2 commits
  10. 19 Jan, 2015 1 commit
  11. 15 Jan, 2015 2 commits
  12. 22 Oct, 2014 1 commit
    • Fix test assertions · 7a5072c5
      Vinnie Okada authored
      Make sure we're asserting the correct thing when testing visible and
      invisible DOM elements.
  13. 18 Oct, 2014 3 commits
  14. 16 Oct, 2014 1 commit
  15. 22 Sep, 2014 1 commit
  16. 07 Aug, 2014 1 commit
  17. 14 Jun, 2014 1 commit
  18. 24 May, 2014 1 commit
  19. 22 May, 2014 1 commit
  20. 13 Apr, 2014 1 commit
  21. 19 Mar, 2014 1 commit
    • Speed up features/notes_on_merge_requests_spec · 53d3294d
      Robert Speicher authored
      This spec featured the slowest tests in the entire suite. After some
      debugging, the cause was found to be the large commit diff generated by
      comparing the stable and master branches.
      
      To fix this, the seed repository was modified to create a simple branch
      off of master that consists of three simple commits and minor changes.
      The spec was then updated to compare master to this branch instead of
      stable. The result is a spec group that runs in under 30 seconds, down
      from about 90.
  22. 24 Feb, 2014 1 commit
  23. 23 Jan, 2014 1 commit
  24. 22 Jan, 2014 1 commit
  25. 01 Jan, 2014 1 commit
  26. 26 Dec, 2013 1 commit
  27. 09 Oct, 2013 1 commit
  28. 11 Sep, 2013 1 commit
  29. 18 Jul, 2013 3 commits
    • Rebased on 6.0 · 128f2845
      Izaak Alpert authored
      -Had to do some minor test clean up as well
      
      Change-Id: I8f378f1b5fe676d73b8691e870c11ca6def90cbf
    • MR on Fork multiple fixes · 489fa5d7
      Izaak Alpert authored
      -Disable observers post test run
      -Allow db:seed_fu RAILS_ENV=test to be run more than once without error
      -fix diffs_in_between, was passing in the default_options for grit, but grit in this case doesn't take options, fixed the test to actually fail if the incorrect diffs are returned
      -make notes/commits render against proper project
      -MR discussion file links should reference note's project
      -Added tests for commit links on edit merge request
      -fixes edit issues (canceling an edited mr, updating an edited mr)
      -updates tests with checks for source code updates
      -still forked_merge_requests.feature (project_forked_merge_requests) test not passing (commented out -- "stable" not being set)
      
      MR API: error on bad target_project
      
      -If the target project id is specified and it is not the same as the project the request is being made on (the source), and the it isn't a fork of that project, error out, otherwise use it as the target
      -Fixes some busted (but hidden) test cases
      
      Conflicts:
      	app/views/merge_requests/show/_diffs.html.haml
      	spec/features/notes_on_merge_requests_spec.rb
      
      Change-Id: I20e595c156d0e8a63048baaead7be6330c738a05
    • 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
  30. 10 Jul, 2013 2 commits
  31. 01 Jul, 2013 1 commit
  32. 11 Apr, 2013 1 commit