- 03 Apr, 2017 1 commit
-
-
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.
-
- 27 Mar, 2017 1 commit
-
-
Robert Speicher authored
-
- 23 Feb, 2017 2 commits
-
-
Douwe Maan authored
This reverts commit cb10b725c8929b8b4460f89c9d96c773af39ba6b.
-
Douwe Maan authored
-
- 04 Dec, 2016 1 commit
-
-
Z.J. van de Weg authored
-
- 01 Dec, 2016 1 commit
-
-
Robert Speicher authored
-
- 21 Oct, 2016 1 commit
-
- 18 Oct, 2016 1 commit
-
-
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.
-
- 17 Oct, 2016 6 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
This reverts commit 1404aa86.
-
Lin Jen-Shin authored
- 14 Oct, 2016 1 commit
-
- 08 Oct, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 23 Sep, 2016 3 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 14 Sep, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 13 Sep, 2016 1 commit
-
-
Lin Jen-Shin authored
-