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

Orphaned/zombie releases #6763

New Issue
Closed
opened 2025-11-02 07:05:54 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 07:05:54 -06:00
Owner
Copy Link

Originally created by @pat-s on GitHub (Jan 26, 2021).

  • Gitea version (or commit ref): 1.13.1
  • Git version: 2.26.0
  • Operating system: docker
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
  • Log gist:

Description

In some repo imports from GitLab (not a recent import) we have orphaned/zombie releases, meaning they show up in the "releases" section and one can click on them/their tag, but their redirect back to the main page of that repo.

I tried finding and deleting these releases via the API however they are not listed as releases (not even the tags exist).

I am wondering how I can get rid of these zombie objects?

Do I need to remove them within the DB somehow?

Screenshots

image
Originally created by @pat-s on GitHub (Jan 26, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.io/en-us/faq) 5. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.13.1 - Git version: 2.26.0 - Operating system: docker - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - Log gist: ## Description In some repo imports from GitLab (not a recent import) we have orphaned/zombie releases, meaning they show up in the "releases" section and one can click on them/their tag, but their redirect back to the main page of that repo. I tried finding and deleting these releases via the API however they are not listed as releases (not even the tags exist). I am wondering how I can get rid of these zombie objects? Do I need to remove them within the DB somehow? ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> <img width="296" alt="image" src="https://user-images.githubusercontent.com/8430564/105860056-78974700-5fed-11eb-827e-8dd85ee2b3a7.png">
GiteaMirror added the type/bug label 2025-11-02 07:05:54 -06:00
GiteaMirror commented 2025-11-02 07:05:55 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 26, 2021):

If there is no release notes that means they are just tags, I think you can delete from database safely.

@lunny commented on GitHub (Jan 26, 2021): If there is no release notes that means they are just tags, I think you can delete from database safely.
GiteaMirror commented 2025-11-02 07:05:55 -06:00
Author
Owner
Copy Link

@pat-s commented on GitHub (Jan 26, 2021):

Thanks!

git push --delete origin <tagname>

did it.

@pat-s commented on GitHub (Jan 26, 2021): Thanks! ``` git push --delete origin <tagname> ``` did it.
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#6763
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?