1. 03 Mar, 2014 3 commits
  2. 25 Feb, 2014 1 commit
  3. 19 Feb, 2014 2 commits
    • Pierre de La Morinerie's avatar
      Send emails from the author · 96dded3e
      Pierre de La Morinerie authored
      This changes the email "From" field from "gitlab@example.com" to either:
      
      * "John Doe <gitlab@example.com>" if the author of the action is known,
      * "GitLab <gitlab@example.com>" otherwise.
      
      Rationale: this allow mails to appear as if they were sent by the
      author. It appears in the mailbox more like a real discussion between
      the sender and the receiver ("John sent: we should refactor this") and
      less like a robot notifying about something.
      96dded3e
    • Pierre de La Morinerie's avatar
      Remove the email subject prefix · 44ab156e
      Pierre de La Morinerie authored
      This changes email subjects from:
      
          GitLab | Team / Project | Note for issue #1234
      
      to:
      
          Team / Project | Note for issue #1234
      
      Rationale:
      
      * Emails should be as meaningful as possible, and emphasize content over
      chrome. The "GitLab" name is more chrome than content.
      
      * Users can tell an email coming from GitLab by the sender or the header
      in the email content.
      
      * An organization that works mainly with GitLab knows that
      every SVC email comes from GitLab. For these organizations, having
      "GitLab" in front of every email is just noise hiding the meaningful
      information.
      44ab156e
  4. 14 Feb, 2014 1 commit
    • Jason Hollingsworth's avatar
      Add email aliases for users · 29cfd33d
      Jason Hollingsworth authored
      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.
      29cfd33d
  5. 22 Jan, 2014 1 commit
  6. 18 Dec, 2013 1 commit
  7. 08 Nov, 2013 2 commits
  8. 08 Oct, 2013 1 commit
  9. 12 Sep, 2013 1 commit
  10. 26 Aug, 2013 1 commit
  11. 22 Aug, 2013 1 commit
  12. 20 Aug, 2013 1 commit
  13. 18 Jul, 2013 1 commit
    • 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
  14. 24 Jun, 2013 1 commit
  15. 22 Jun, 2013 1 commit
  16. 14 Jun, 2013 1 commit
  17. 01 Apr, 2013 1 commit
  18. 28 Mar, 2013 1 commit
  19. 19 Mar, 2013 2 commits
  20. 01 Feb, 2013 1 commit
  21. 18 Jan, 2013 1 commit
  22. 15 Jan, 2013 1 commit
  23. 31 Dec, 2012 1 commit
  24. 23 Nov, 2012 1 commit
  25. 13 Nov, 2012 1 commit
  26. 13 Oct, 2012 1 commit
  27. 06 Sep, 2012 1 commit
  28. 02 Sep, 2012 1 commit
  29. 29 Aug, 2012 1 commit
  30. 26 Aug, 2012 1 commit
  31. 21 Aug, 2012 1 commit
  32. 11 Aug, 2012 1 commit
  33. 06 Aug, 2012 1 commit
  34. 02 Jul, 2012 2 commits