- 01 Oct, 2015 1 commit
-
-
Stan Hu authored
Closes #2867
-
- 21 Sep, 2015 1 commit
-
-
Douwe Maan authored
-
- 09 Sep, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 26 Aug, 2015 1 commit
-
-
Douwe Maan authored
-
- 19 Aug, 2015 6 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 18 Aug, 2015 1 commit
-
-
Douwe Maan authored
-
- 06 May, 2015 2 commits
-
-
Dmitriy Zaporozhets authored
-
Jakub Jirutka authored
-
- 25 Apr, 2015 1 commit
-
-
Robert Speicher authored
Closes internal https://dev.gitlab.org/gitlab/gitlabhq/issues/2269
-
- 14 Apr, 2015 1 commit
-
-
Douwe Maan authored
-
- 03 Apr, 2015 1 commit
-
-
Stan Hu authored
Closes #1305
-
- 02 Apr, 2015 1 commit
-
-
Douwe Maan authored
-
- 25 Mar, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 11 Mar, 2015 1 commit
-
-
Vyacheslav Slinko authored
-
- 25 Feb, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
See #1809.
-
- 07 Feb, 2015 2 commits
-
-
Douwe Maan authored
Closes #1932.
-
Aleks Bunin authored
Fixes #8748.
-
- 18 Jan, 2015 1 commit
-
-
Steven Burgart authored
signe-in -> signed-in go_to_gihub_for_permissions -> go_to_github_for_permissions descendand -> descendant behavour -> behaviour recepient_email -> recipient_email generate_fingerpint -> generate_fingerprint dependes -> depends Cant't -> Can't wisit -> visit notifcation -> notification sufficent_scope -> sufficient_scope? levet -> level
-
- 04 Dec, 2014 1 commit
-
-
Marin Jankovski authored
-
- 11 Nov, 2014 1 commit
-
-
Marin Jankovski authored
-
- 03 Jul, 2014 1 commit
-
-
Pierre de La Morinerie authored
* send a 'In-Reply-To' header along the 'References' header * subject of answers to an existing thread begins with 'Re: '
-
- 18 Jun, 2014 1 commit
-
-
Jacob Vosmaer authored
This reverts commit 97fd990e, reversing changes made to f451a697. Conflicts: app/mailers/emails/notes.rb app/mailers/emails/projects.rb
-
- 10 Jun, 2014 2 commits
-
-
Pierre de La Morinerie authored
* send a ‘In-Reply-To’ header along the ‘References’ header * subject of answers to an existing thread begins with ‘Re: ’ This fixes threading with at least Mail.app and Airmail.
-
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.
-
- 05 May, 2014 1 commit
-
-
Philip Blatter authored
Added email threading for update emails on issues and merge requests (if the mail client support the References: mail header)
-
- 19 Feb, 2014 4 commits
-
-
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.
-
Pierre de La Morinerie authored
For instance, the email "Subject" field changes from: Mattt / Ground Control | Saving issue doesn't work sometimes (#1234) to: Ground Control | Saving issue doesn't work sometimes (#1234) Rationale: * Most people are receiving email notifications about a single fork: the project activity, issues and merge requests are happening either in a root repository or in a fork, but less often in several forks. * It removes noise from the email subject. The namespace of the project can still be read in the email body. * For Entreprise users that have a single namespace "MyEntreprise", having this repeated in every email subject is very noisy.
-
Pierre de La Morinerie authored
This changes email subjects from: GitLab | Team / Project | Note for issue #1234 to: Team / Project | Note for issue #1234 Rationale: * Emails should be as meaningful as possible, and emphasize content over chrome. The "GitLab" name is more chrome than content. * Users can tell an email coming from GitLab by the sender or the header in the email content. * An organization that works mainly with GitLab knows that every SVC email comes from GitLab. For these organizations, having "GitLab" in front of every email is just noise hiding the meaningful information.
-
Pierre de La Morinerie authored
-
- 25 Jan, 2014 1 commit
-
-
Jason Hollingsworth authored
A test was broken if running on a non-standard port. Made checking for (non-)standard port more robust. Changed gitlab_on_non_standard_port to gitlab_on_standard_port (less negative).
-
- 09 Dec, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 11 Sep, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-
- 18 Jul, 2013 1 commit
-
-
Izaak Alpert authored
Forked MR's will print Project:Branch <source_project_with_path>:<source_branch> -> <target_project_with_path>:<target_branch> Non forked MR's will print Branch <source_branch> -> <target_branch> Change-Id: I89399aec2e7fde8e4b64b110a48099a95ae4f038
-
- 19 Mar, 2013 1 commit
-
-
Dmitriy Zaporozhets authored
-