Skip to content
Snippets Groups Projects
  1. Jul 21, 2015
  2. Jun 26, 2015
  3. Jun 05, 2015
    • Jeroen van Baarsen's avatar
      Update noteable after a new note is added · fbdaf0e2
      Jeroen van Baarsen authored
      
      **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: username-removed-1164's avatarJeroen van Baarsen <jeroenvanbaarsen@gmail.com>
      fbdaf0e2
  4. May 11, 2015
  5. Apr 24, 2015
  6. Apr 16, 2015
  7. Mar 19, 2015
  8. Feb 12, 2015
  9. Nov 05, 2014
  10. Oct 10, 2014
  11. Oct 06, 2014
  12. Oct 03, 2014
  13. Sep 15, 2014
  14. Sep 14, 2014
  15. Jun 26, 2014
  16. Apr 09, 2014
  17. Apr 03, 2014
  18. Feb 07, 2014
  19. Jan 22, 2014
  20. Jan 06, 2014
  21. Nov 28, 2013
  22. Oct 01, 2013
  23. 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
  24. Aug 21, 2013
  25. Jul 18, 2013
    • 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
  26. Jun 19, 2013
  27. Jan 15, 2013
  28. Jan 05, 2013
  29. Jan 04, 2013
  30. Jan 03, 2013
  31. Dec 18, 2012
  32. Dec 03, 2012
  33. Nov 19, 2012
  34. Nov 13, 2012
  35. Oct 13, 2012
  36. Oct 09, 2012
Loading