gitlab-org--gitlab-foss/app/views/notify/new_merge_request_email.html.haml

%p.details
  != merge_path_description(@merge_request, '&rarr;')

- if @merge_request.assignee_id.present?
  %p
    Assignee: #{@merge_request.author_name} &rarr; #{@merge_request.assignee_name}

-if @merge_request.description
  = markdown(@merge_request.description)
Simplify the default layout of notification emails * Less margin: the content appears as the text of the message. * Streamlined footer: everything on one line, with a small separator. * Zimbra (www.zimbra.com) chokes on HTML tables, and doesn't display the content of the message. Switching to a simpler layout fixes the issue. 2014-02-18 08:27:39 -05:00			`%p.details`
Update emails to describe path using for_fork? 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 2013-07-17 10:35:11 -04:00			`!= merge_path_description(@merge_request, '→')`
Notification when created merge request 2011-12-17 11:07:28 -05:00
Add the description to the "new issue" and "new merge request" emails Previously the content of the issue or merge request was missing from the email. 2014-02-18 08:44:00 -05:00			`- if @merge_request.assignee_id.present?`
			`%p`
			`Assignee: #{@merge_request.author_name} → #{@merge_request.assignee_name}`

			`-if @merge_request.description`
			`= markdown(@merge_request.description)`