5 Commits (216c8eada3c0727288dc5565ae9fdd798b17c463)

Author	SHA1	Message	Date
Giteabot	ac91bb27ff	Fix markdown rendering when mentioning users (#30795) (#30810) ... Backport #30795 by wxiaoguang Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>	10 months ago
wxiaoguang	18dd9f9a3f	Fix label rendering (#30456) ... 1. Check whether the label is for an issue or a pull request. 2. Don't use space to layout 3. Make sure the test strings have trailing spaces explicitly, to avoid some IDE removing the trailing spaces automatically.	11 months ago
KN4CK3R	85c59d6c21	Use relative links for commits, mentions, and issues in markdown (#29427) ... Fixes #29404 Use relative links for - commits - mentions - issues --------- Co-authored-by: silverwind <me@silverwind.io>	12 months ago
KN4CK3R	637451a45e	Rework markup link rendering (#26745) ... Fixes #26548 This PR refactors the rendering of markup links. The old code uses `strings.Replace` to change some urls while the new code uses more context to decide which link should be generated. The added tests should ensure the same output for the old and new behaviour (besides the bug). We may need to refactor the rendering a bit more to make it clear how the different helper methods render the input string. There are lots of options (resolve links / images / mentions / git hashes / emojis / ...) but you don't really know what helper uses which options. For example, we currently support images in the user description which should not be allowed I think: <details> <summary>Profile</summary> https://try.gitea.io/KN4CK3R  </details> --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>	1 year ago
Jason Song	59d2189875	Fix missing commit message body when the message has leading newlines (#25418) ... Commit with `echo "\nmessage after a blank line\nsecond line of the message" | git commit --cleanup=verbatim -F -` and push. <img width="1139" alt="image" src="https://github.com/go-gitea/gitea/assets/9418365/f9a2c28c-e307-4c78-9e31-3d3ace7b9274">	2 years ago