BigW Consortium Gitlab

  1. 25 Mar, 2016 2 commits
    • Improve and finish the fallback to the In-Reply-To and References header for the… · 9f218fc1
      Rémy Coutable authored
      Improve and finish the fallback to the In-Reply-To and References header for the reply-by-email feature
      
      A few things to note:
      - The IncomingEmail feature is now enabled even without a
        correctly-formatted sub-address
      - Message-ID for new thread mail are kept the same so that subsequent
        notifications to this thread are grouped in the thread by the email
        service that receives the notification
        (i.e. In-Reply-To of the answer == Message-ID of the first thread message)
      - To maximize our chance to be able to retrieve the reply key, we look
        for it in the In-Reply-To header and the References header
      - The pattern for the fallback reply message id is "reply-[key]@[gitlab_host]"
      - Improve docs thanks to Axil
  2. 19 Jan, 2016 1 commit
  3. 09 Jan, 2016 1 commit
  4. 15 Dec, 2015 1 commit
  5. 10 Dec, 2015 1 commit
  6. 08 Dec, 2015 1 commit
  7. 01 Oct, 2015 1 commit
  8. 21 Sep, 2015 1 commit
  9. 09 Sep, 2015 1 commit
  10. 26 Aug, 2015 1 commit
  11. 19 Aug, 2015 6 commits
  12. 18 Aug, 2015 1 commit
  13. 06 May, 2015 2 commits
  14. 25 Apr, 2015 1 commit
  15. 14 Apr, 2015 1 commit
  16. 03 Apr, 2015 1 commit
  17. 02 Apr, 2015 1 commit
  18. 25 Mar, 2015 1 commit
  19. 11 Mar, 2015 1 commit
  20. 25 Feb, 2015 2 commits
  21. 07 Feb, 2015 2 commits
  22. 18 Jan, 2015 1 commit
    • Fix various typos · 5c801602
      Steven Burgart authored
      signe-in -> signed-in
      go_to_gihub_for_permissions -> go_to_github_for_permissions
      descendand -> descendant
      behavour -> behaviour
      recepient_email -> recipient_email
      generate_fingerpint -> generate_fingerprint
      dependes -> depends
      Cant't -> Can't
      wisit -> visit
      notifcation -> notification
      sufficent_scope -> sufficient_scope?
      levet -> level
  23. 04 Dec, 2014 1 commit
  24. 11 Nov, 2014 1 commit
  25. 03 Jul, 2014 1 commit
  26. 18 Jun, 2014 1 commit
  27. 10 Jun, 2014 2 commits
    • 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.
    • 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.
  28. 05 May, 2014 1 commit
  29. 19 Feb, 2014 2 commits
    • 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.
    • Don't write the project namespace in email subjects · d8a24003
      Pierre de La Morinerie authored
      For instance, the email "Subject" field changes from:
      
          Mattt / Ground Control | Saving issue doesn't work sometimes (#1234)
      
      to:
      
          Ground Control | Saving issue doesn't work sometimes (#1234)
      
      Rationale:
      
      * Most people are receiving email notifications about a single fork:
      the project activity, issues and merge requests are happening either
      in a root repository or in a fork, but less often in several forks.
      
      * It removes noise from the email subject. The namespace of the project
      can still be read in the email body.
      
      * For Entreprise users that have a single namespace "MyEntreprise",
      having this repeated in every email subject is very noisy.