BigW Consortium Gitlab

  1. 01 Oct, 2015 1 commit
  2. 21 Sep, 2015 1 commit
  3. 09 Sep, 2015 1 commit
  4. 26 Aug, 2015 1 commit
  5. 19 Aug, 2015 6 commits
  6. 18 Aug, 2015 1 commit
  7. 06 May, 2015 2 commits
  8. 25 Apr, 2015 1 commit
  9. 14 Apr, 2015 1 commit
  10. 03 Apr, 2015 1 commit
  11. 02 Apr, 2015 1 commit
  12. 25 Mar, 2015 1 commit
  13. 11 Mar, 2015 1 commit
  14. 25 Feb, 2015 2 commits
  15. 07 Feb, 2015 2 commits
  16. 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
  17. 04 Dec, 2014 1 commit
  18. 11 Nov, 2014 1 commit
  19. 03 Jul, 2014 1 commit
  20. 18 Jun, 2014 1 commit
  21. 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.
  22. 05 May, 2014 1 commit
  23. 19 Feb, 2014 4 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.
    • 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.
    • Fix misleading comment · 49cb1c72
      Pierre de La Morinerie authored
  24. 25 Jan, 2014 1 commit
  25. 09 Dec, 2013 1 commit
  26. 11 Sep, 2013 1 commit
  27. 18 Jul, 2013 1 commit
    • Update emails to describe path using for_fork? · 539c70c7
      Izaak Alpert authored
      Forked MR's will print
      
      Project:Branch <source_project_with_path>:<source_branch> -> <target_project_with_path>:<target_branch>
      
      Non forked MR's will print
      
      Branch <source_branch> -> <target_branch>
      
      Change-Id: I89399aec2e7fde8e4b64b110a48099a95ae4f038
  28. 19 Mar, 2013 1 commit