Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link to issues in other repositories #6264

Closed
exploide opened this issue Mar 7, 2019 · 0 comments · Fixed by #6273
Closed

Link to issues in other repositories #6264

exploide opened this issue Mar 7, 2019 · 0 comments · Fixed by #6273
Labels
topic/ui Change the appearance of the Gitea UI

Comments

@exploide
Copy link

exploide commented Mar 7, 2019

  • Gitea version (or commit ref): 1.7.0

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 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.

@techknowlogick techknowlogick added the topic/ui Change the appearance of the Gitea UI label Mar 7, 2019
mrsdizzie added a commit to mrsdizzie/gitea that referenced this issue Mar 28, 2019
Update autolinks to match what github does here:

Issue in same repo: #1
Issue in different repo: org/repo#1

Fixes go-gitea#6264
lafriks pushed a commit that referenced this issue Apr 12, 2019
* 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
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
topic/ui Change the appearance of the Gitea UI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants