- 09 Aug, 2016 1 commit
-
-
Lin Jen-Shin authored
Closes #20724
-
- 06 Jul, 2016 1 commit
-
-
Douwe Maan authored
-
- 15 Jun, 2016 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 23 May, 2016 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 21 May, 2016 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
- 20 May, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 18 May, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 16 May, 2016 14 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
sent_notification.project would never be nil, and we also have already checked message_project before entering process_create_issue.
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
So we extend Gitlab::Email::Receiver for this new behaviour, however we might want to split it into another class for better testing it. Another issue is that, currently it's using this to parse project identifier: Gitlab::IncomingEmail.key_from_address Which is using: Gitlab.config.incoming_email.address for the receiver name. This is probably `reply` because it's used for replying to a specific issue. We might want to introduce another config for this, or just use `reply` instead of `incoming`. I'll prefer to introduce a new config for this, or just change `reply` to `incoming` because it would make sense for replying to there, too. The email template used in tests were copied and modified from: `emails/valid_reply.eml` which I hope is ok.
-
- 25 Mar, 2016 2 commits
-
-
Rémy Coutable authored
Improve and finish the fallback to the In-Reply-To and References header for the reply-by-email feature A few things to note: - The IncomingEmail feature is now enabled even without a correctly-formatted sub-address - Message-ID for new thread mail are kept the same so that subsequent notifications to this thread are grouped in the thread by the email service that receives the notification (i.e. In-Reply-To of the answer == Message-ID of the first thread message) - To maximize our chance to be able to retrieve the reply key, we look for it in the In-Reply-To header and the References header - The pattern for the fallback reply message id is "reply-[key]@[gitlab_host]" - Improve docs thanks to Axil
-
David Padilla authored
-
- 23 Mar, 2016 1 commit
-
-
Lin Jen-Shin authored
-
- 07 Jan, 2016 1 commit
-
-
Douwe Maan authored
-
- 21 Sep, 2015 1 commit
-
-
Douwe Maan authored
-
- 20 Sep, 2015 1 commit
-
-
Douwe Maan authored
-
- 21 Aug, 2015 1 commit
-
-
Douwe Maan authored
-
- 20 Aug, 2015 4 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-