Jan Provaznik b39b5524f2 Use message body for merge request description ... 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		2017-12-11 11:46:21 +01:00
..
android_gmail.eml	…
attachment.eml	…
auto_reply.eml	…
commands_in_reply.eml	…
commands_only_reply.eml	…
dutch.eml	…
forwarded_new_issue.eml	…
gmail_web.eml	…
html_empty_link.eml	…
html_paragraphs.eml	…
inline_reply.eml	…
ios_default.eml	…
newlines.eml	…
no_content_reply.eml	…
on_wrote.eml	…
outlook.eml	…
outlook_html.eml	…
paragraphs.eml	…
plaintext_only.eml	…
reply_without_subaddressing_and_key_inside_references.eml	…
reply_without_subaddressing_and_key_inside_references_with_a_comma.eml	…
valid_new_issue.eml	…
valid_new_issue_empty.eml	…
valid_new_merge_request.eml	Use message body for merge request description	2017-12-11 11:46:21 +01:00
valid_new_merge_request_no_description.eml	Use message body for merge request description	2017-12-11 11:46:21 +01:00
valid_new_merge_request_no_subject.eml	…
valid_reply.eml	…
windows_8_metro.eml	…
wrong_incoming_email_token.eml	…
wrong_mail_key.eml	…