Render markdown bodies in emails #289

New Issue

GiteaMirror · 2025-11-02T03:17:26-06:00

GiteaMirror commented

2025-11-02 03:17:26 -06:00

Originally created by @mjwwit on GitHub (Jan 26, 2017).

Description

Notification emails being sent after issues are created contain the body of the issue. Generally speaking, markdown formatting is used to structure the body of issues, and Gitea renders this perfectly fine. The notification emails though, contain the unformatted markdown content. Gitea should render the body to HTML before putting it in the emails to improve readability.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/41348528-render-markdown-bodies-in-emails?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github).

Originally created by @mjwwit on GitHub (Jan 26, 2017). ## Description Notification emails being sent after issues are created contain the body of the issue. Generally speaking, markdown formatting is used to structure the body of issues, and Gitea renders this perfectly fine. The notification emails though, contain the unformatted markdown content. Gitea should render the body to HTML before putting it in the emails to improve readability. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/41348528-render-markdown-bodies-in-emails?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>

GiteaMirror added the type/enhancement label 2025-11-02 03:17:26 -06:00

GiteaMirror closed this issue

2025-11-02 03:17:26 -06:00

GiteaMirror commented

2025-11-02 03:17:27 -06:00

@bkcsoft commented on GitHub (Feb 12, 2017):

I think we already do this. We send both a text/plain and text/html in the emails. And test/html should be rendered correctly.

@bkcsoft commented on GitHub (Feb 12, 2017): I think we already do this. We send both a `text/plain` and `text/html` in the emails. And `test/html` should be rendered correctly.

GiteaMirror commented

2025-11-02 03:17:27 -06:00

@mjwwit commented on GitHub (Feb 13, 2017):

@bkcsoft Yes, there is a text/plain and a text/html version of the mail. The only rendered markup are links to issues/PRs though, and any other formatting seems to be sent as is. This looks extra chaotic because rendered html doesn't honor linebreaks in the source. I should have fixed the rendering of all markdown formatting in #803, but @lunny still got a text/plain email. I will do further debugging to see if I can resolve that.

@mjwwit commented on GitHub (Feb 13, 2017): @bkcsoft Yes, there is a `text/plain` and a `text/html` version of the mail. The only rendered markup are links to issues/PRs though, and any other formatting seems to be sent as is. This looks extra chaotic because rendered html doesn't honor linebreaks in the source. I should have fixed the rendering of all markdown formatting in #803, but @lunny still got a `text/plain` email. I will do further debugging to see if I can resolve that.

GiteaMirror commented

2025-11-02 03:17:27 -06:00

@mjwwit commented on GitHub (Feb 26, 2017):

Fixed by #1027

@mjwwit commented on GitHub (Feb 26, 2017): Fixed by #1027

GiteaMirror referenced this issue

2025-11-02 11:43:11 -06:00

[PR #289] [MERGED] Golint fixed for models/issue_comment.go #15287

Sign in to join this conversation.