BigW Consortium Gitlab

  1. 18 Oct, 2016 1 commit
    • Use bcc for pipeline emails because: · 045c6715
      Lin Jen-Shin authored
      We use bcc here because we don't want to generate this emails for a
      thousand times. This could be potentially expensive in a loop, and
      recipients would contain all project watchers so it could be a lot.
  2. 14 Oct, 2016 2 commits
  3. 08 Oct, 2016 1 commit
  4. 07 Oct, 2016 1 commit
  5. 06 Oct, 2016 2 commits
  6. 03 Oct, 2016 1 commit
  7. 26 Sep, 2016 1 commit
  8. 13 Sep, 2016 1 commit
  9. 31 Aug, 2016 3 commits
  10. 26 Aug, 2016 1 commit
  11. 15 Aug, 2016 1 commit
  12. 12 Aug, 2016 1 commit
  13. 29 Jul, 2016 1 commit
  14. 15 Jul, 2016 1 commit
  15. 06 Jul, 2016 3 commits
  16. 20 Jun, 2016 1 commit
  17. 16 Jun, 2016 2 commits
  18. 14 Jun, 2016 5 commits
  19. 03 Jun, 2016 2 commits
  20. 17 May, 2016 1 commit
  21. 11 May, 2016 1 commit
    • Only generate repository push email once · 5f27e26b
      Sean McGivern authored
      The repository push email can be very expensive to generate, especially
      with syntax-highlighted diffs. Instead of generating the email for each
      recipient, generate one email object and reset the Message-Id and To
      headers for each recipient. (Cloning would also be expensive in the case
      of large emails, although probably not as bad as generating from
      scratch.)
  22. 02 May, 2016 1 commit
  23. 19 Apr, 2016 1 commit
  24. 17 Mar, 2016 1 commit
  25. 15 Mar, 2016 4 commits