1. 05 8月, 2015 1 次提交
  2. 26 6月, 2015 1 次提交
  3. 05 6月, 2015 1 次提交
    • J
      Update noteable after a new note is added · fbdaf0e2
      Jeroen van Baarsen 提交于
      **What does this do?**
      It makes sure that whenever a new note is added to an noteable item, the
      updated_at of that item is also updated.
      
      **Why is this needed?**
      At this moment when you post a comment on an issue or add a label to an issue,
      the updated_at is not changed. Because of this the filtering for least recently
      updated is not really useful (since it only takes in account the original text
      from the noteable).
      Signed-off-by: NJeroen van Baarsen <jeroenvanbaarsen@gmail.com>
      fbdaf0e2
  4. 11 5月, 2015 3 次提交
  5. 24 4月, 2015 2 次提交
  6. 17 4月, 2015 1 次提交
  7. 19 3月, 2015 1 次提交
  8. 13 2月, 2015 1 次提交
  9. 05 11月, 2014 1 次提交
  10. 10 10月, 2014 2 次提交
  11. 06 10月, 2014 1 次提交
  12. 04 10月, 2014 1 次提交
  13. 15 9月, 2014 2 次提交
  14. 27 6月, 2014 1 次提交
  15. 09 4月, 2014 1 次提交
  16. 03 4月, 2014 1 次提交
  17. 07 2月, 2014 1 次提交
  18. 23 1月, 2014 1 次提交
  19. 07 1月, 2014 1 次提交
  20. 29 11月, 2013 1 次提交
  21. 01 10月, 2013 1 次提交
  22. 26 8月, 2013 1 次提交
    • A
      Link issues from comments and automatically close them · c8a115c0
      ash wilson 提交于
      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
  23. 21 8月, 2013 1 次提交
  24. 18 7月, 2013 1 次提交
    • I
      Merge Request on forked projects · 3d7194f0
      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
      3d7194f0
  25. 19 6月, 2013 1 次提交
  26. 15 1月, 2013 1 次提交
  27. 05 1月, 2013 2 次提交
  28. 04 1月, 2013 1 次提交
  29. 19 12月, 2012 1 次提交
  30. 04 12月, 2012 1 次提交
  31. 20 11月, 2012 1 次提交
  32. 13 11月, 2012 1 次提交
  33. 13 10月, 2012 1 次提交
  34. 09 10月, 2012 1 次提交