21 Feb, 2014

1 commit


13 Feb, 2014

1 commit

  • Emails are used to associate commits with users. The emails
    are not verified and don't have to be valid email addresses. They
    are assigned on a first come, first serve basis.
    
    Notifications are sent when an email is added.
    Jason Hollingsworth
     

28 Jan, 2014

1 commit


22 Jan, 2014

2 commits


18 Jan, 2014

1 commit


18 Dec, 2013

1 commit


17 Dec, 2013

2 commits


16 Dec, 2013

2 commits


04 Dec, 2013

1 commit

  • Next fields were added:
    * push_events
    * issues_events
    * merge_requests_events
    
    Main goal is to create web hooks that can be triggered only for certain
    event types. For example you can have separate web hook for push events
    and another one for issues.
    
    Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
    Dmitriy Zaporozhets
     

26 Nov, 2013

1 commit


12 Nov, 2013

1 commit


06 Nov, 2013

1 commit


15 Oct, 2013

1 commit


09 Oct, 2013

1 commit


26 Sep, 2013

1 commit


09 Sep, 2013

1 commit


01 Sep, 2013

1 commit


25 Aug, 2013

1 commit

  • 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

2 commits


19 Aug, 2013

1 commit


12 Aug, 2013

1 commit


08 Aug, 2013

2 commits


04 Aug, 2013

1 commit


30 Jul, 2013

1 commit


17 Jul, 2013

1 commit

  • 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
     

12 Jul, 2013

1 commit


24 Jun, 2013

1 commit


22 Jun, 2013

2 commits


21 Jun, 2013

1 commit


18 Jun, 2013

3 commits


14 Jun, 2013

2 commits