gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2016-10-21	Test against notification email	Lin Jen-Shin

2016-10-18	Use bcc for pipeline emails because:	Lin Jen-Shin
	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.
2016-10-17	should_email_no_one -> should_not_email_anyone, feedback:	Lin Jen-Shin
	https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6342/diffs#note_17039876
2016-10-17	Introduce email_recipients and use include? Feedback:	Lin Jen-Shin
	https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6342#note_16075554 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6342#note_16075622
2016-10-17	Try to slightly optimize EmailHeleprs	Lin Jen-Shin

2016-10-17	Use EmailHelpers where possible, feedback:	Lin Jen-Shin
	https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6342#note_15434860
2016-08-16	DRY up the added update service specs, add two email helpers	Nick Thomas

2016-03-15	Original implementation to allow users to subscribe to labels	Timothy Andrew
	1. Allow subscribing (the current user) to a label - Refactor the `Subscription` coffeescript class - The main change is that it accepts a container, and conducts all DOM queries within its scope. We need this because the labels page has multiple instances of `Subscription` on the same page. 2. Creating an issue or MR with labels notifies users subscribed to those labels - Label `has_many` subscribers through subscriptions. 3. Adding a label to an issue or MR notifies users subscribed to those labels - This only applies to subscribers of the label that has just been added, not all labels for the issue.