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

Why did I not merge to the master/main? It also shows that the branches have been merged #9969

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

Originally created by @coverthesea on GitHub (Dec 13, 2022).

Feature Description

Only after I merge to main should it be displayed that I have merged
Now I just merge to the test branch, which also shows that the branch has been merged
Is this a different design?

Screenshots

No response

Originally created by @coverthesea on GitHub (Dec 13, 2022). ### Feature Description Only after I merge to main should it be displayed that I have merged Now I just merge to the test branch, which also shows that the branch has been merged Is this a different design? ### Screenshots _No response_
GiteaMirror added the type/proposalissue/needs-feedback labels 2025-11-02 08:54:36 -06:00
GiteaMirror commented 2025-11-02 08:54:37 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 14, 2022):

But like Gitea has main, release/** may contains some commits from some branch. We don't know which branches should we stick.

@lunny commented on GitHub (Dec 14, 2022): But like Gitea has `main`, `release/**` may contains some commits from some branch. We don't know which branches should we stick.
GiteaMirror commented 2025-11-02 08:54:37 -06:00
Author
Owner
Copy Link

@coverthesea commented on GitHub (Dec 14, 2022):

I think it is generally the default branch
Similar to gitlab
I use gitlab now. Merged will be displayed only when merging to the main branch
I think it should be the default branch set

@coverthesea commented on GitHub (Dec 14, 2022): > I think it is generally the default branch Similar to gitlab I use gitlab now. Merged will be displayed only when merging to the main branch I think it should be the default branch set
GiteaMirror commented 2025-11-02 08:54:38 -06:00
Author
Owner
Copy Link

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

I didn't get the point about why "Merged should only be displayed when merging to the main branch".

What benefits does it bring?

Without some real cases, I also think current Gitea's approach is good enough: merged means that the new branch has been merged into another branch.

@wxiaoguang commented on GitHub (May 12, 2023): I didn't get the point about why "Merged should only be displayed when merging to the main branch". What benefits does it bring? Without some real cases, I also think current Gitea's approach is good enough: merged means that the new branch has been merged into another branch.
GiteaMirror commented 2025-11-02 08:54:38 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Sep 8, 2023):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Sep 8, 2023): We close issues that need feedback from the author if there were no new comments for a month. :tea:
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/needs-feedback type/proposal
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#9969
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?