Markdown elements in PRs will be rendered #66

Open
opened 2022-07-30 21:27:04 +00:00 by delvh · 1 comment
delvh commented 2022-07-30 21:27:04 +00:00 (Migrated from gitea.com)

At the moment, if a PR title has markdown elements (~~, **, _, ...), they will destroy the formatting of that PR.
I don't know if there's anything we can do about that as Markdown can't be escaped as far as I know...

Noticed by Allow custom default merge message with .gitea/default_merge_message/<merge_style>_TEMPLATE.md being rendered italically (https://github.com/go-gitea/gitea/pull/18177 )

At the moment, if a PR title has markdown elements (`~~`, `**`, `_`, ...), they will destroy the formatting of that PR. I don't know if there's anything we can do about that as Markdown can't be escaped as far as I know... Noticed by `Allow custom default merge message with .gitea/default_merge_message/<merge_style>_TEMPLATE.md` being rendered italically (https://github.com/go-gitea/gitea/pull/18177 )
jolheiser commented 2022-07-31 01:40:16 +00:00 (Migrated from gitea.com)

Did a quick test, and there are some caveats.

You can escape markdown with a backslash, however it gets tricky because _this_ works but \_this\_ does not.

Did a quick test, and there are some caveats. You _can_ escape markdown with a backslash, however it gets tricky because \_this\_ works but `\_this\_` does not.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: lunny/changelog#66
No description provided.