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

Incorrect dashboard link to a tag of a mirror repository #7169

New Issue
Closed
opened 2025-11-02 07:18:12 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 07:18:12 -06:00
Owner
Copy Link

Originally created by @wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf on GitHub (Apr 13, 2021).

  • Gitea version (or commit ref): Gitea Version: 1.15.0+dev-126-g66f0fd095
  • Git version: git version 2.31.1.394.g7d1e84936f
  • Operating system: Arch Linux
  • Built from: sources
  • Ran with: systemd
  • Database:
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • tbh haven't tried but I'm pretty sure this applies there, too

Description

I've got mirrors of some GH repos on my Gitea instance and syncing and everything has been working brilliantly.

Links to newly synced tag references are shown "as synced", that is:
wanderer synced new reference refs/tags/2021-04-13 to wanderer/exploitdb from mirror
with "wanderer" being my user and "exploitdb" being the name of the repo I'm mirroring.

This would be all be just right, however, what's problematic is that the link underneath refs/tags/... points to
{GIT-DOT-DOMAIN-DOT-TLD}/wanderer/exploitdb/src/refs/tags/2021-04-13.
As you can see, this is not the structure Gitea uses for displaying tags, the correct one would be
{GIT-DOT-DOMAIN-DOT-TLD}/wanderer/exploitdb/src/tag/2021-04-13,
which, when manually overwritten in the address bar (or clicked through the webui), correctly shows the tag tree.

A similar issue exists with displaying/linking to Gitlab's merge request refs, but I am not quite sure what would need to be done there.
In this case Gitea syncs the refs and shows:
mirror synced new reference refs/merge-requests/355/head to {repo} and
mirror synced new reference refs/merge-requests/355/merge to {repo} (with {repo} being just a placeholder here),
which obviously Gitea doesn't know what to do with.
Here it'd probably suffice to extract the commit hash from the head and create a link using that...

Originally created by @wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf on GitHub (Apr 13, 2021). - Gitea version (or commit ref): ` Gitea Version: 1.15.0+dev-126-g66f0fd095` - Git version: `git version 2.31.1.394.g7d1e84936f` - Operating system: Arch Linux - Built from: `sources` - Ran with: `systemd` - Database: - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] tbh haven't tried but I'm pretty sure this applies there, too ## Description I've got mirrors of some GH repos on my Gitea instance and syncing and everything has been working brilliantly. Links to newly synced tag references are shown "as synced", that is: `wanderer synced new reference refs/tags/2021-04-13 to wanderer/exploitdb from mirror` with "wanderer" being my user and "exploitdb" being the name of the repo I'm mirroring. This would be all be just right, however, what's problematic is that the link underneath `refs/tags/...` points to `{GIT-DOT-DOMAIN-DOT-TLD}/wanderer/exploitdb/src/refs/tags/2021-04-13`. As you can see, this is not the structure Gitea uses for displaying tags, the correct one would be `{GIT-DOT-DOMAIN-DOT-TLD}/wanderer/exploitdb/src/tag/2021-04-13`, which, when manually overwritten in the address bar (or clicked through the webui), correctly shows the tag tree. A similar issue exists with displaying/linking to Gitlab's merge request refs, but I am not quite sure what would need to be done there. In this case Gitea syncs the refs and shows: `mirror synced new reference refs/merge-requests/355/head to {repo}` and `mirror synced new reference refs/merge-requests/355/merge to {repo}` (with `{repo}` being just a placeholder here), which obviously Gitea doesn't know what to do with. Here it'd probably suffice to extract the commit hash from the head and create a link using *that*...
GiteaMirror added the type/bug label 2025-11-02 07:18:12 -06:00
GiteaMirror commented 2025-11-02 07:18:13 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 2, 2024):

I think this has been resolved.

@lunny commented on GitHub (Mar 2, 2024): I think this has been resolved.
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#7169
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?