- 11 Dec, 2017 1 commit
-
-
Jan Provaznik authored
When a merge request is created from email, use message body as merge request description. If message body is empty then merge request description is still created from the source branch commit (if there is only single commit in the merge request). If message body is empty and there are multiple commits in the source branch, then merge request description is left empty. Closes #40968
-
- 05 Dec, 2017 1 commit
-
-
Jan Provaznik authored
* new merge request can be created by sending an email to the specific email address (similar to creating issues by email) * for the first iteration, source branch must be specified in the mail subject, other merge request parameters can not be set yet * user should enable "Receive notifications about your own activity" in user settings to receive a notification about created merge request Part of #32878
-
- 16 Nov, 2017 1 commit
-
-
Jacopo authored
Adds a rubocop rule (with autocorrect) to ensure line break after guard clauses.
-
- 03 Aug, 2017 1 commit
-
-
Lin Jen-Shin authored
This would be much more accurate. We assume this is an auto-generated email if such header is provided, and the value is not "no". It could also be: "auto-generated", "auto-replied", or other values from extension. It seems that only "no" could mean that this is sent by a human. See: https://tools.ietf.org/html/rfc3834
-
- 02 Aug, 2017 1 commit
-
-
Lin Jen-Shin authored
Also make it easier to have mailer helper
-
- 01 Aug, 2017 1 commit
-
-
Gabriel Mazetto authored
-
- 07 Jul, 2017 1 commit
-
-
Douwe Maan authored
-
- 05 Jul, 2017 1 commit
-
-
Douwe Maan authored
-
- 19 Jun, 2017 1 commit
-
-
http://jneen.net/ authored
-
- 29 May, 2017 1 commit
-
-
Douwe Maan authored
-
- 05 May, 2017 1 commit
-
-
Sean McGivern authored
`Project#inspect` isn't very useful for examining usage of these features.
-
- 03 May, 2017 1 commit
-
-
Sean McGivern authored
These set the 'actual' destination email in one of the Delivered-To lines, so check those too.
-
- 02 May, 2017 1 commit
-
-
Jarka Kadlecova authored
-
- 01 May, 2017 1 commit
-
-
Sean McGivern authored
If an email doesn't match our incoming email patterns on the To header, we fall back to the References header. If there was no References header, we'd raise an exception, when we'd be better off acting as if it was empty.
-
- 21 Apr, 2017 1 commit
-
-
Sean McGivern authored
-
- 20 Apr, 2017 2 commits
-
-
Sean McGivern authored
-
Sean McGivern authored
This lets us track how many incoming emails a GitLab instance is processing, by email type (handler) and by project (where applicable).
-
- 07 Apr, 2017 1 commit
-
-
Felipe Artur authored
-
- 05 Apr, 2017 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 01 Mar, 2017 1 commit
-
-
Sean McGivern authored
-
- 23 Feb, 2017 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 07 Feb, 2017 1 commit
-
-
Z.J. van de Weg authored
-
- 03 Feb, 2017 2 commits
-
-
Adam Pahlevi authored
add complete changelog for !8949
- 20 Jan, 2017 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
Microsoft Exchange would append a comma and another message id into the References header, therefore we'll need to fallback and parse the header by ourselves. Closes #26567
-
- 13 Jan, 2017 1 commit
-
-
Pawel Chojnacki authored
- allows unsubscription processing of email in format "reply+%{key}+unsubscribe@acme.com" (example) - if config.address includes %{key} and replies are enabled every unsubscriable message will include mailto: link in its List-Unsubscribe header
-
- 22 Dec, 2016 1 commit
-
-
http://jneen.net/ authored
-
- 21 Dec, 2016 7 commits
-
-
http://jneen.net/ authored
-
http://jneen.net/ authored
This reverts commit 4f2f678aff8d7dfcac96c47cf7eb480a5707ddaf.
-
http://jneen.net/ authored
-
http://jneen.net/ authored
-
http://jneen.net/ authored
-
http://jneen.net/ authored
-
http://jneen.net/ authored
-
- 16 Dec, 2016 1 commit
-
-
Rydkin Maxim authored
-
- 17 Nov, 2016 1 commit
-
-
http://jneen.net/ authored
-