You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a comment, when referencing an issue from an other repository, e.g. https://git.example.org/MyOrg/wood/issues/119 it is rendered as #119, even when it links to the other repository, and not the one I'm currently commenting. This is a bit confusing.
GitHub solves this by rendering wood/#119 in this case (or even OtherOrg/wood/#119 when within another organisation). Would be great if Gitea adopts this.
Hopefully I correctly searched for duplicates. Have not found something like this.
The text was updated successfully, but these errors were encountered:
* Improve issue autolinks
Update autolinks to match what github does here:
Issue in same repo: #1
Issue in different repo: org/repo#1
Fixes#6264
* Use setting.AppURL when parsing URL
Using setting.AppURL here is a more reliable way of parsing the current
URL and what other functions in this file seem to use.
* Make ComposeMetas always return a valid context
* Add per repository markdown renderers for better context
* Update for use of context metas
Now that we include the user and repo name inside context metas, update
various code and tests for this new logic
Description
In a comment, when referencing an issue from an other repository, e.g.
https://git.example.org/MyOrg/wood/issues/119
it is rendered as#119
, even when it links to the other repository, and not the one I'm currently commenting. This is a bit confusing.GitHub solves this by rendering
wood/#119
in this case (or evenOtherOrg/wood/#119
when within another organisation). Would be great if Gitea adopts this.Hopefully I correctly searched for duplicates. Have not found something like this.
The text was updated successfully, but these errors were encountered: