17 Jul, 2013

1 commit

  • 3d7194f0   Merge Request on forked projects ... Browse Dir » 
    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
     

15 Jul, 2013

2 commits

13 Jul, 2013

1 commit

22 Jun, 2013

2 commits

19 Jun, 2013

2 commits

18 Jun, 2013

2 commits

17 Jun, 2013

1 commit

16 Jun, 2013

1 commit

14 Jun, 2013

2 commits

12 Jun, 2013

1 commit

11 Jun, 2013

1 commit

06 Jun, 2013

1 commit

05 Jun, 2013

3 commits

04 Jun, 2013

1 commit

24 May, 2013

1 commit

22 May, 2013

1 commit

19 May, 2013

1 commit

13 May, 2013

1 commit

09 May, 2013

2 commits

07 May, 2013

1 commit

06 May, 2013

1 commit

05 May, 2013

1 commit

03 May, 2013

1 commit

02 May, 2013

2 commits

  • f40d4e66   Merge pull request #3597 from amacarthur/fork-pull-request ... Browse Dir » 
    updated fork feature to use gitlab-shell for v5 of gitlab
    Dmitriy Zaporozhets
     
  • 4c44c5ef   Internally public projects ... Browse Dir » 
    Public projects listed in the public section will be linked to the
actual project's page. Public projects now give any user Guest
permissions to the project, allowing them to download the code, read
and create issues, and view anything else in the project's pages.

Ample access tests have been added to the project_access_spec to
verify correct permissions and behavior on public projects.
- Visitors to the site who are not logged in still cannot view the
  project's pages.
- Logged-in users visiting a public project where they are not a team
  member can create issues, but not snippets. They can view the projects
  code, issues, merge requests, etc, just as if they were a Guest member
  of the project.
- Since this is a public project, the user is also granted :download_code
  permissions, a permission normally reserved for Reporters, since they
  can clone the repo anyways and browse commits and branches locally.
    Stephen Lottermoser
     

25 Apr, 2013

1 commit

15 Apr, 2013

1 commit

12 Apr, 2013

1 commit

11 Apr, 2013

2 commits

03 Apr, 2013

2 commits