BigW Consortium Gitlab

  1. 01 Oct, 2015 1 commit
  2. 25 May, 2015 1 commit
  3. 06 May, 2015 2 commits
  4. 24 Apr, 2015 1 commit
  5. 14 Apr, 2015 5 commits
  6. 02 Apr, 2015 1 commit
  7. 23 Mar, 2015 2 commits
  8. 18 Mar, 2015 1 commit
  9. 10 Mar, 2015 1 commit
  10. 25 Feb, 2015 6 commits
  11. 14 Feb, 2015 1 commit
    • 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.
  12. 07 Feb, 2015 1 commit
  13. 15 Sep, 2014 1 commit
  14. 14 Sep, 2014 1 commit
  15. 18 Jun, 2014 1 commit
  16. 15 Jun, 2014 1 commit
  17. 10 Jun, 2014 1 commit
    • 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.
  18. 11 Apr, 2014 1 commit
  19. 03 Mar, 2014 1 commit
    • 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.
  20. 19 Feb, 2014 1 commit
    • 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.
  21. 12 Feb, 2014 1 commit
  22. 17 Dec, 2013 3 commits
  23. 08 Nov, 2013 1 commit
    • 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. :)
  24. 11 Sep, 2013 1 commit
  25. 22 Jun, 2013 1 commit
  26. 19 Mar, 2013 1 commit