Feature Description
Currently, the auto-generated release notes in Gitea use explicit Markdown links for pull request references, for example:
* Some change in [#123](https://example.com/repo/pulls/123)
While this works functionally, there is a noticeable difference in behavior compared to GitHub that affects both readability and UX.
On GitHub, auto-generated release notes also rely on full URLs internally, but the rendered result behaves like a “smart reference”: #123 is displayed as a clickable reference, and hovering over it shows a preview popup with PR details such as title and author.
In Gitea, however, [#123](url) is treated as a standard Markdown link. It does not behave like an issue/PR reference and does not provide the hover preview popup. In contrast, when #123 is written directly as a plain reference, Gitea correctly applies automatic linking and enables the hover preview.
This creates an inconsistency where manually written references provide richer interaction than auto-generated release notes.
Screenshots
No response
Feature Description
Currently, the auto-generated release notes in Gitea use explicit Markdown links for pull request references, for example:
While this works functionally, there is a noticeable difference in behavior compared to GitHub that affects both readability and UX.
On GitHub, auto-generated release notes also rely on full URLs internally, but the rendered result behaves like a “smart reference”:
#123is displayed as a clickable reference, and hovering over it shows a preview popup with PR details such as title and author.In Gitea, however,
[#123](url)is treated as a standard Markdown link. It does not behave like an issue/PR reference and does not provide the hover preview popup. In contrast, when#123is written directly as a plain reference, Gitea correctly applies automatic linking and enables the hover preview.This creates an inconsistency where manually written references provide richer interaction than auto-generated release notes.
Screenshots
No response