Skip to content
Snippets Groups Projects
  1. Oct 09, 2013
  2. Aug 27, 2013
  3. Aug 25, 2013
    • ash wilson's avatar
      Link issues from comments and automatically close them · c8a115c0
      ash wilson authored
      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.
      c8a115c0
  4. Aug 08, 2013
  5. Jul 30, 2013
  6. Jul 24, 2013
  7. Jul 18, 2013
    • Izaak Alpert's avatar
      Rebase on master · 09112dbb
      Izaak Alpert authored
      Trying to retrigger travis
      Change-Id: Ifd86fb4c6b2791ad176230254fbf69a9ade979fb
      09112dbb
    • Izaak Alpert's avatar
      Fix intermittently failing notification_service test · 216d5e2c
      Izaak Alpert authored
      Change-Id: Ic23cb46901f8adc77943bf3cc79566587364e22a
      216d5e2c
    • Izaak Alpert's avatar
      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
      3d7194f0
  8. Jun 24, 2013
  9. Apr 10, 2013
  10. Apr 01, 2013
  11. Mar 28, 2013
  12. Mar 26, 2013
  13. Mar 12, 2013
  14. Feb 25, 2013
  15. Feb 20, 2013
Loading