21 Nov, 2013

1 commit

13 Nov, 2013

1 commit

12 Nov, 2013

2 commits

06 Nov, 2013

1 commit

05 Nov, 2013

2 commits

04 Nov, 2013

1 commit

  • c46eaca9   More escaping ... Browse Dir » 
    - Database name may contain characters which are not shell friendly
- Database password could contain the same
- While we at it there is no harm in escaping generated paths too
- Refactored 2-line system(command)

Signed-off-by: Nigel Kukard <nkukard@lbsd.net>
    Nigel Kukard
     

16 Oct, 2013

1 commit

15 Oct, 2013

1 commit

14 Oct, 2013

1 commit

11 Oct, 2013

2 commits

09 Oct, 2013

1 commit

07 Oct, 2013

1 commit

04 Oct, 2013

1 commit

01 Oct, 2013

1 commit

29 Sep, 2013

1 commit

26 Sep, 2013

1 commit

22 Sep, 2013

2 commits

17 Sep, 2013

1 commit

14 Sep, 2013

1 commit

13 Sep, 2013

1 commit

12 Sep, 2013

1 commit

11 Sep, 2013

1 commit

09 Sep, 2013

1 commit

25 Aug, 2013

1 commit

  • c8a115c0   Link issues from comments and automatically close them ... Browse Dir » 
    Any mention of Issues, MergeRequests, or Commits via GitLab-flavored markdown
references in descriptions, titles, or attached Notes creates a back-reference
Note that links to the original referencer. Furthermore, pushing commits with
commit messages that match a (configurable) regexp to a project's default
branch will close any issues mentioned by GFM in the matched closing phrase.
If accepting a merge request would close any Issues in this way, a banner is
appended to the merge request's main panel to indicate this.
    ash wilson
     

21 Aug, 2013

3 commits

20 Aug, 2013

2 commits

13 Aug, 2013

1 commit

09 Aug, 2013

1 commit

30 Jul, 2013

1 commit

29 Jul, 2013

1 commit

17 Jul, 2013

3 commits

  • fae3f466   Refactor merge api create ... Browse Dir » 
    -Made the api method a little more readable
-removed some missed extra newline's

Change-Id: Ic38baafc813aaeda0a8b283f39916182c8ec37d5
    Izaak Alpert
     
  • 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
     
  • aa0473d0   Validate fingerprint uniqueness Browse Dir »
    Jacob Vosmaer