github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-09 04:25:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Cross-referencing issues from other repos results in URLs pointing to wrong issue tracker #10964

New Issue
Open
opened 2025-11-02 09:23:28 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 09:23:28 -06:00
Owner
Copy Link

Originally created by @sebthom on GitHub (Jun 5, 2023).

Description

Lets say we have these repos in different orgs:

  • org1/repo1
  • org2/repo2

In a pull request to org1/repo1 we want to reference an issue located in the issue tracker of org2/repo2 in the PR description using the short hand syntax org2/repo2#100. The rendered HTML URL rendered however wrongly points to the issue tracker in org1/repo1 instead of org2/repo2: https://<gitea_host>/org1/repo1/issues/100

Interestingly referencing a PR of the other repo works as expected. E.g.
org2/repo2!200 will be rendered as https://<gitea_host>/org2/repo2/pulls/200

Gitea Version

1.19.3

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

Dockerized

Database

SQLite

Originally created by @sebthom on GitHub (Jun 5, 2023). ### Description Lets say we have these repos in different orgs: - org1/repo1 - org2/repo2 In a pull request to **org1/repo1** we want to reference an issue located in the issue tracker of **org2/repo2** in the PR description using the short hand syntax `org2/repo2#100`. The rendered HTML URL rendered however wrongly points to the issue tracker in **org1/repo1** instead of **org2/repo2**: `https://<gitea_host>/org1/repo1/issues/100` Interestingly referencing a PR of the other repo works as expected. E.g. `org2/repo2!200` will be rendered as `https://<gitea_host>/org2/repo2/pulls/200` ### Gitea Version 1.19.3 ### Can you reproduce the bug on the Gitea demo site? Yes ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? Dockerized ### Database SQLite
GiteaMirror added the type/bug label 2025-11-02 09:23:28 -06:00
GiteaMirror commented 2025-11-02 09:23:29 -06:00
Author
Owner
Copy Link

@sebthom commented on GitHub (Jun 5, 2023):

Same issue when referencing issues from other org/repos in e.g. CHANGELOG.md files using the syntax <org><repo>#<issue_id>

@sebthom commented on GitHub (Jun 5, 2023): Same issue when referencing issues from other org/repos in e.g. CHANGELOG.md files using the syntax `<org><repo>#<issue_id>`
GiteaMirror commented 2025-11-02 09:23:29 -06:00
Author
Owner
Copy Link

@Zettat123 commented on GitHub (Aug 31, 2023):

Hi @sebthom, I cannot reproduce this bug in v1.19.3 or the main branch. If possible, could you please provide more detailed steps to reproduce?

@Zettat123 commented on GitHub (Aug 31, 2023): Hi @sebthom, I cannot reproduce this bug in v1.19.3 or the main branch. If possible, could you please provide more detailed steps to reproduce?
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 type/bug
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#10964
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?