An error occurred fetching the project authors.
  1. 02 Nov, 2018 1 commit
  2. 23 Oct, 2018 1 commit
  3. 24 Sep, 2018 2 commits
  4. 11 Sep, 2018 2 commits
  5. 15 Aug, 2018 1 commit
  6. 20 Jun, 2018 1 commit
    • Mark Chao's avatar
      Notify only when unmergeable due to conflict · 5b994b81
      Mark Chao authored
      There is still the edge case when 'no commits' changes to 'conflict'
      would not trigger notification, which we ignore for now.
      
      Calling can_be_merged? can cause exception (e.g. non-UTF8)
      Ignore those by rescueing.
      
      Remove unmergeable_reason as now only conflict is notified
      
      Update spec
      5b994b81
  7. 24 May, 2018 1 commit
  8. 18 May, 2018 2 commits
  9. 17 May, 2018 2 commits
  10. 03 Apr, 2018 1 commit
  11. 26 Mar, 2018 1 commit
  12. 19 Jan, 2018 1 commit
  13. 18 Jan, 2018 1 commit
    • Mario de la Ossa's avatar
      Initial work to add notification reason to emails · fd360602
      Mario de la Ossa authored
      Adds `#build_notification_recipients` to `NotificationRecipientService`
      that returns the `NotificationRecipient` objects in order to be able to
      access the new attribute `reason`.
      
      This new attribute is used in the different notifier methods in order to
      add the reason as a header: `X-GitLab-NotificationReason`.
      
      Only the reason with the most priority gets sent.
      fd360602
  14. 17 Jan, 2018 1 commit
    • Mario de la Ossa's avatar
      Initial work to add notification reason to emails · 23a20c20
      Mario de la Ossa authored
      Adds `#build_notification_recipients` to `NotificationRecipientService`
      that returns the `NotificationRecipient` objects in order to be able to
      access the new attribute `reason`.
      
      This new attribute is used in the different notifier methods in order to
      add the reason as a header: `X-GitLab-NotificationReason`.
      
      Only the reason with the most priority gets sent.
      23a20c20
  15. 05 Jul, 2017 2 commits
  16. 17 Jan, 2017 3 commits
  17. 16 Jan, 2017 1 commit
  18. 19 Aug, 2016 1 commit
  19. 17 Aug, 2016 1 commit
    • Robert Speicher's avatar
      Merge branch '2451-fix-mentions-in-issue-updates' into 'master' · 0e5ac6f9
      Robert Speicher authored
      Send notification emails when users are newly mentioned in issue or MR edits
      
      ## What does this MR do?
      
      Introduces "new mention in issue" and "new mention in MR" email notifications.  Editing a Mentionable title or description and adding a mention to a user who was not previously mentioned will now send them a notification email, following usual permissions for doing so.
      
      ## Why was this MR needed?
      
      Issues & MRs may be edited to include mentions to new people. We don't currently send out email notifications of these edits to anyone, although they do create TODOs. This brings email notifications into parity with TODOs.
      
      ## What are the relevant issue numbers?
      
      Closes #2451
      
      See merge request !5800
      0e5ac6f9
  20. 15 Aug, 2016 1 commit
  21. 29 Jul, 2016 1 commit
  22. 12 Jul, 2016 1 commit
  23. 20 Jun, 2016 1 commit
  24. 19 Apr, 2016 1 commit
  25. 15 Mar, 2016 3 commits
  26. 15 Jan, 2016 1 commit
  27. 09 Jan, 2016 1 commit
  28. 19 Aug, 2015 2 commits
  29. 18 Aug, 2015 1 commit
  30. 14 Feb, 2015 1 commit
    • Vinnie Okada's avatar
      Upgrade to Rails 4.1.9 · 76aad9b7
      Vinnie Okada authored
      Make the following changes to deal with new behavior in Rails 4.1.2:
      
      * Use nested resources to avoid slashes in arguments to path helpers.
      76aad9b7