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

Default branch can be missing on releases tab #7841

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

Originally created by @delvh on GitHub (Sep 13, 2021).

Description

Apparently, the default branch can be missing on the release page of projects.
This seems to be a backend issue because the generated link is https://gitea.com/xorm/xorm/compare/v1.2.2... as well and hence missing the branch to compare with.
When I disable JavaScript, the result is still the same.

Screenshots

image

Originally created by @delvh on GitHub (Sep 13, 2021). - Gitea version (or commit ref): 1.16.0+dev-209-g9fa6bdb64 - Can you reproduce the bug at https://try.gitea.io: not sure, was noticed on https://gitea.com/xorm/xorm/releases ## Description Apparently, the default branch can be missing on the release page of projects. This seems to be a backend issue because the generated link is `https://gitea.com/xorm/xorm/compare/v1.2.2...` as well and hence missing the branch to compare with. When I disable JavaScript, the result is still the same. ## Screenshots ![image](https://user-images.githubusercontent.com/51889757/133160612-7de738d9-752d-4e48-938a-023d017d275d.png)
GiteaMirror added the type/bug label 2025-11-02 07:38:53 -06:00
GiteaMirror commented 2025-11-02 07:38:54 -06:00
Author
Owner
Copy Link

@a1012112796 commented on GitHub (Sep 14, 2021):

maybe Target of these Release is missing in db. But don't know why.
hasen't found this bug on the latest commit (1.16.0+dev-239-g04b233e94)

@a1012112796 commented on GitHub (Sep 14, 2021): maybe `Target` of these `Release` is missing in db. But don't know why. hasen't found this bug on the latest commit (`1.16.0+dev-239-g04b233e94`)
GiteaMirror commented 2025-11-02 07:38:54 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (May 12, 2023):

Related to #24470 and #24148

I think this issue has been fixed.

@wxiaoguang commented on GitHub (May 12, 2023): Related to #24470 and #24148 I think this issue has been fixed.
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#7841
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?