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

[Feature Request] Highlight active forks #12624

New Issue
Open
opened 2025-11-02 10:16:22 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 10:16:22 -06:00
Owner
Copy Link

Originally created by @Darthagnon on GitHub (Mar 10, 2024).

Feature Description

Currently, Gitea displays commits ahead/behind, last commit, user and timestamp per branch on a project. Would it be possible to display something similar for the Forks view of said project? This would help a lot with finding active forks of a project.

It would also be nice if commits ahead/behind was listed in the titlebar of a forked repo, similar to the Github UI.

Screenshots

Something like this, but for the Forks view:
chrome_240310_09

Something like this (per fork rather than per branch?):
chrome_240310_10

Originally created by @Darthagnon on GitHub (Mar 10, 2024). ### Feature Description Currently, Gitea displays commits ahead/behind, last commit, user and timestamp per branch on a project. Would it be possible to display something similar for the Forks view of said project? This would help a lot with finding active forks of a project. It would also be nice if commits ahead/behind was listed in the titlebar of a forked repo, similar to the Github UI. ### Screenshots Something like this, but for the Forks view: ![chrome_240310_09](https://github.com/go-gitea/gitea/assets/20792748/924a5d37-ab07-43b0-afb2-ca03f13f4296) Something like this (per fork rather than per branch?): ![chrome_240310_10](https://github.com/go-gitea/gitea/assets/20792748/6fff98c6-6801-4c63-ac0d-cc4286a5fa4e)
GiteaMirror added the type/proposal label 2025-11-02 10:16:22 -06:00
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/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#12624
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?