github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-16 04:42:51 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Link to issues in other repositories #3018

New Issue
Closed
opened 2025-11-02 04:57:33 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 04:57:33 -06:00
Owner
Copy Link

Originally created by @exploide on GitHub (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.

Originally created by @exploide on GitHub (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.
GiteaMirror added the topic/ui label 2025-11-02 04:57:33 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/ui
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3018
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?