BigW Consortium Gitlab

  1. 03 Apr, 2017 1 commit
    • Quiet pipeline emails · a1805cbc
      Sean McGivern authored
      1. Never send a pipeline email to anyone other than the user who created
         the pipeline.
      2. Only send pipeline success emails to people with the custom
         notification setting for enabled. Watchers and participants will
         never receive this.
      3. When custom settings are unset (for new settings and legacy ones),
         act as if failed_pipeline is set.
  2. 27 Mar, 2017 1 commit
  3. 23 Feb, 2017 2 commits
  4. 04 Dec, 2016 1 commit
  5. 01 Dec, 2016 1 commit
  6. 21 Oct, 2016 1 commit
  7. 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.
  8. 17 Oct, 2016 6 commits
  9. 14 Oct, 2016 1 commit
  10. 08 Oct, 2016 1 commit
  11. 23 Sep, 2016 3 commits
  12. 14 Sep, 2016 1 commit
  13. 13 Sep, 2016 1 commit