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

Links to commits in comments don't update after repo transfer #2722

New Issue
Closed
opened 2025-11-02 04:45:36 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 04:45:36 -06:00
Owner
Copy Link

Originally created by @jaroel on GitHub (Jan 8, 2019).

Hi,

When I transfer a repo to another org, then existing links to commits in comments are not updated to reflect that change.

I've seen this in Gitea Version: 1.4.3 .

Originally created by @jaroel on GitHub (Jan 8, 2019). Hi, When I transfer a repo to another org, then existing links to commits in comments are not updated to reflect that change. I've seen this in Gitea Version: 1.4.3 .
GiteaMirror added the issue/confirmedtype/bug labels 2025-11-02 04:45:36 -06:00
GiteaMirror commented 2025-11-02 04:45:37 -06:00
Author
Owner
Copy Link

@jaroel commented on GitHub (Jan 8, 2019):

I'm guessing I'm confused, because a full link to a commit looks just like a link with just the commit hash.
In a comment https://git.uwkm.nl/jan/niet_voor_jos/commit/ccc6f31b176915a86c5ea617da71e612c3a95c37 and ccc6f31b176915a86c5ea617da71e612c3a95c37 look the same (ccc6f31b17), but aren't.

So this actual issue might be that full links to commits aren't converted to just the hash?

@jaroel commented on GitHub (Jan 8, 2019): I'm guessing I'm confused, because a full link to a commit looks just like a link with just the commit hash. In a comment `https://git.uwkm.nl/jan/niet_voor_jos/commit/ccc6f31b176915a86c5ea617da71e612c3a95c37` and `ccc6f31b176915a86c5ea617da71e612c3a95c37` look the same (`ccc6f31b17`), but aren't. So this actual issue might be that full links to commits aren't converted to just the hash?
GiteaMirror commented 2025-11-02 04:45:37 -06:00
Author
Owner
Copy Link

@jaroel commented on GitHub (Jan 8, 2019):

Sorry, nope. Any hash will link to the current repo, even if it isn't a commit in the repo.

@jaroel commented on GitHub (Jan 8, 2019): Sorry, nope. Any hash will link to the current repo, even if it isn't a commit in the repo.
GiteaMirror commented 2025-11-02 04:45:37 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Mar 9, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 9, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:45:37 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 28, 2024):

Closing as outdated.

@lunny commented on GitHub (Feb 28, 2024): Closing as outdated.
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 issue/confirmed 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#2722
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?