Distinguish active branches from stale branches #9200

New Issue

GiteaMirror · 2025-11-02T08:32:06-06:00

GiteaMirror commented

2025-11-02 08:32:06 -06:00

Originally created by @jpraet on GitHub (Jul 8, 2022).

Feature Description

Currently the gitea branch list view shows the default branch, followed by a paginated list of all other branches sorted alphabetically.

This view is hard to navigate if you have a lot of branches. It would be better to distinguish the active branches from the stale branches, as also done on github. I also think it makes more sense to sort them by descending latest modification date, as users are generally more likely to be looking for those recently updated branches.

Screenshots

Originally created by @jpraet on GitHub (Jul 8, 2022). ### Feature Description Currently the gitea branch list view shows the default branch, followed by a paginated list of all other branches sorted alphabetically. This view is hard to navigate if you have a lot of branches. It would be better to distinguish the active branches from the stale branches, as also done on github. I also think it makes more sense to sort them by descending latest modification date, as users are generally more likely to be looking for those recently updated branches. ### Screenshots ![image](https://user-images.githubusercontent.com/2212615/178031961-adf0ded8-f67f-4b38-8d62-f529d487bf8c.png)

GiteaMirror added the type/feature type/proposal labels 2025-11-02 08:32:06 -06:00

GiteaMirror commented

2025-11-02 08:32:06 -06:00

@jpraet commented on GitHub (Jul 8, 2022):

Relates to #12763

@jpraet commented on GitHub (Jul 8, 2022): Relates to #12763

GiteaMirror commented

2025-11-02 08:32:07 -06:00

@lunny commented on GitHub (Jun 28, 2023):

related to #22743 and we need to know what's the stale's definition. 1 year ago branches should be considered as stale?

@lunny commented on GitHub (Jun 28, 2023): related to #22743 and we need to know what's the `stale`'s definition. 1 year ago branches should be considered as `stale`?

GiteaMirror commented

2025-11-02 08:32:07 -06:00

@lunny commented on GitHub (Apr 30, 2025):

Branches are currently sorted by their latest update time. If we define active and stale based on the last updated time, would that be sufficient?

@lunny commented on GitHub (Apr 30, 2025): Branches are currently sorted by their latest update time. If we define `active` and `stale` based on the last updated time, would that be sufficient?

GiteaMirror commented

2025-11-02 08:32:07 -06:00

@jpraet commented on GitHub (Apr 30, 2025):

For reference, on GitHub: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository

Stale branches: The Stale view shows all branches that no one has committed to in the last three months, ordered by the branches with the oldest commits first.

@jpraet commented on GitHub (Apr 30, 2025): For reference, on GitHub: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/viewing-branches-in-your-repository Stale branches: The Stale view shows all branches that no one has committed to in the last three months, ordered by the branches with the oldest commits first.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#9200