19 Aug, 2013

1 commit


15 Aug, 2013

1 commit

  • Ref: https://github.com/gitlabhq/gitlabhq/commit/e6159b8725f99af78f446f8d33fa0e52b7780430
    Ref: https://github.com/gitlabhq/gitlabhq/pull/3204
    Ref: https://github.com/gitlabhq/gitlabhq/issues/1228
    
    Add Rails' variable in application.rb to support relative url
    
    This variable is used by assets compilation and other modules.
    
    Note that user needs to change application.rb too
    
    Restrict session cookie to the relative path if set.
    
    Ref: https://github.com/gitlabhq/gitlabhq/commit/2c2f1e31856a4decdae469974f5bea8245316f7e
    
    Fix Update attachment_uploader.rb bug with relative URL
    
    See: https://github.com/gitlabhq/gitlabhq/commit/161afda3fa4fca58f396e9c3acbd72bc14490ace
    
    Fix Wall relative bug with attachement files (javascript)
    amouhzi
     

14 Aug, 2013

2 commits


13 Aug, 2013

1 commit


08 Aug, 2013

2 commits


05 Aug, 2013

3 commits


04 Aug, 2013

3 commits


02 Aug, 2013

2 commits


30 Jul, 2013

7 commits


29 Jul, 2013

1 commit


18 Jul, 2013

1 commit


17 Jul, 2013

7 commits

  • -Fixed tests to account for this
    -Trigger update after update_branches for list:update selecting first commit, have it also trigger sha lookup
    
    Change-Id: Ie4c3d4fbf57aeadd7d141d3704f4ea0f0684a7a5
    Izaak Alpert
     
  • -Made the api method a little more readable
    -removed some missed extra newline's
    
    Change-Id: Ic38baafc813aaeda0a8b283f39916182c8ec37d5
    Izaak Alpert
     
  • -Some changes around calling origional methods for !for_fork? merge requests. Other changes to follow
    
    Change-Id: I009c716ce2475b9efa3fd07aee9215fca7a1c150
    Izaak Alpert
     
  • -Removed many extra spaces I added
    -Fixed email templates to be consistent/better looking
    
    GITLAB-894, GITLAB-895, (GITLAB-858)
    
    Change-Id: I35c1a8e0e22af7de26d54e5c3da987fa7bb3921e
    Izaak Alpert
     
  • -The forked merge request test now tests it's componenets again, and seems to work every time (did this by reordering the branch updates so their is more time for update_branches to run) -- this could still technically fail, but after several runs it doesn't seem to.
    -Removed todo in merge_request, pushed wrapping of grit down to the satellite
    -updated action test to check flock status, made it nolonger pending
    -moved all logging on failure to helper method in satellite
    GITLAB-592
    
    Change-Id: If0554ca35eedc3d3e8461f7d93d4b3939fa2cd75
    Izaak Alpert
     
  • -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
    Izaak Alpert
     
  • 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
    Izaak Alpert
     

16 Jul, 2013

4 commits


12 Jul, 2013

4 commits


11 Jul, 2013

1 commit