1. 20 Sep, 2015 1 commit
  2. 19 Aug, 2015 2 commits
  3. 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
  4. 03 Jul, 2014 1 commit
  5. 18 Jun, 2014 1 commit
  6. 13 Jun, 2014 1 commit
  7. 10 Jun, 2014 2 commits
    • Pierre de La Morinerie's avatar
      Allow more mail clients to group emails by thread · de90b572
      Pierre de La Morinerie authored
      * send a ‘In-Reply-To’ header along the ‘References’ header
      * subject of answers to an existing thread begins with ‘Re: ’
      
      This fixes threading with at least Mail.app and Airmail.
      de90b572
    • Pierre de La Morinerie's avatar
      Send notification emails to the "project", and put people in Cc · 466b768b
      Pierre de La Morinerie authored
      This fixes email threading in Mail.app, that doesn't like when a thread
      doesn't have stable recipients.
      
      For instance, here is a possible sender-recipient combinations before:
      
      From: A
      To: Me
      New issue
      
      From: B
      To: Me
      Reply on new issue
      
      From: A
      To: Me
      Another reply
      
      Mail.app doesn't see B as a participant to the original email thread,
      and decides to break the thread: it will group all messages from A
      together, and separately all messages from B.
      
      This commit makes the thread look like this:
      
      From: A
      To: gitlab/project
      Cc: Me
      New issue
      
      From: B
      To: gitlab/project
      Cc: Me
      Reply on new issue
      
      From: A
      To: gitlab/project
      Cc: Me
      Another reply
      
      Mail.app sees a common recipient, and group the thread correctly.
      466b768b
  8. 05 May, 2014 2 commits
  9. 28 Apr, 2014 1 commit
  10. 03 Mar, 2014 2 commits
    • Pierre de La Morinerie's avatar
      Remove custom link to target in notification emails · edd6028b
      Pierre de La Morinerie authored
      Every email has a different way of showing a link to the discussion on
      the website. We don't need this anymore, as we now have a standard
      "View in GitLab" link in the footer of every email.
      edd6028b
    • Pierre de La Morinerie's avatar
      Add a "View in GitLab" link in notification emails · 7ba0b502
      Pierre de La Morinerie authored
      When an email notification concerns a specific object (issue, note,
      merge request, etc.), add a link to the footer of the email that opens
      the item's page in a web browser.
      
      Rationale:
      
      * The link is predictable: always the same text, always at the same
      location, like any reliable tool.
      
      * It allows to remove the inline-title in many emails, and leave only
      the actual content of the message.
      7ba0b502
  11. 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
      Write the issue/merge request title in the notification email subject · 57cb1ca7
      Pierre de La Morinerie authored
      This changes the email subjects for issues and merge request
      notifications from:
      
          Team / Project | Note for issue #1234
      
      to:
      
          Team / Project | Saving issue doesn't work sometimes (#1234)
      
      Rationale:
      
      * Scan the subject of the email notification more easily when catching
      up with a lot of notifications. Instead of having to open the email to
      get the title of the issue or merge request, one can simply read the
      subject of the email.
      
      * Group messages by subject: email clients will group emails in threads
      if they have the same subject.
      57cb1ca7
  12. 08 Nov, 2013 1 commit
    • Drew Blessing's avatar
      Fix minor errors/annoyances in email templates · 57ad81a9
      Drew Blessing authored
      There was some funny syntax in merge request email templates. There was a ! before
      the merge request number when there probably should be a #. This may be some carry over
      from markdown but should not be in email templates.  There were also some capitalization
      discrepancies among the subject lines. For those OCD people out there I standardized the
      capitalization. :)
      57ad81a9
  13. 08 Oct, 2013 1 commit
  14. 26 Aug, 2013 1 commit
  15. 31 Mar, 2013 1 commit
  16. 19 Mar, 2013 1 commit