Skip to content
Snippets Groups Projects
  1. Oct 09, 2013
  2. Oct 04, 2013
  3. Sep 03, 2013
  4. Aug 30, 2013
  5. Aug 27, 2013
  6. 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
  7. Aug 23, 2013
  8. Aug 22, 2013
  9. Aug 21, 2013
  10. Aug 19, 2013
  11. Aug 15, 2013
  12. Aug 13, 2013
  13. Aug 10, 2013
  14. Aug 05, 2013
  15. Jul 27, 2013
  16. Jul 18, 2013
    • Izaak Alpert's avatar
      Default allow username or email login to false · d04f3286
      Izaak Alpert authored
      -If not specified in the gitlab.yml default this setting to false
      
      Change-Id: I3551df364498dd84ccbd18c90797522e77159f05
      d04f3286
    • Izaak Alpert's avatar
      Update the proc/lamda to be consistent · 1a31cb2c
      Izaak Alpert authored
      Change-Id: I411c7544c7834b00d26e51dc9a6c0396c51bd4f3
      1a31cb2c
    • Izaak Alpert's avatar
      Allow the ldap logins with email or username · 089605fe
      Izaak Alpert authored
      Change-Id: I73b4aa4c46afd56ae02fb24abcd673c0724547e4
      089605fe
    • 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
  17. Jul 16, 2013
  18. Jul 12, 2013
  19. Jul 08, 2013
Loading