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

Display the branch name in the commit view #2621

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

Originally created by @oto-ledger on GitHub (Dec 5, 2018).

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

Description

Would it be possible to display the branch a commit belongs to when displaying in the commit tab?
When managing multiples branches and having a peer review system, it's quite tedious to make sure the commit being reviewed belongs to a branch or another.
Many thanks,

Screenshots

For example on the try.gitea.io
9ca1d6d82f

We don't even know it's a commit on master (I even haven't checked)

Originally created by @oto-ledger on GitHub (Dec 5, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. 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.6 - Git version: unknown - Operating system: - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description Would it be possible to display the branch a commit belongs to when displaying in the commit tab? When managing multiples branches and having a peer review system, it's quite tedious to make sure the commit being reviewed belongs to a branch or another. Many thanks, ## Screenshots For example on the try.gitea.io https://try.gitea.io/mike/ha-jdbc/commit/9ca1d6d82f3d0d7ba68f738812f84d26f6019df2 We don't even know it's a commit on master (I even haven't checked)
GiteaMirror added the issue/confirmedtype/enhancement labels 2025-11-02 04:42:26 -06:00
GiteaMirror commented 2025-11-02 04:42:27 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 3, 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 (Feb 3, 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:42:27 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Feb 3, 2019):

/reviewed/confirmed

@adelowo commented on GitHub (Feb 3, 2019): /reviewed/confirmed
GiteaMirror commented 2025-11-02 04:42:27 -06:00
Author
Owner
Copy Link

@adelowo commented on GitHub (Feb 4, 2019):

Can this be reopened until https://github.com/go-gitea/gitea/pull/5950 is merged?

@adelowo commented on GitHub (Feb 4, 2019): Can this be reopened until https://github.com/go-gitea/gitea/pull/5950 is merged?
GiteaMirror commented 2025-11-02 04:42:28 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 4, 2019):

Sorry it was closed automatically when the git PR was merged

@zeripath commented on GitHub (Feb 4, 2019): Sorry it was closed automatically when the git PR was merged
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/enhancement
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#2621
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?