Per branch language percents #9961

New Issue

GiteaMirror · 2025-11-02T08:54:21-06:00

GiteaMirror commented

2025-11-02 08:54:21 -06:00

Originally created by @MorsMortium on GitHub (Dec 10, 2022).

Feature Description

It would be nice, if the bar displaying how many percent of the repo is what language, would display the currently selected branch, instead of main. Not sure if this is bug or feature.
An example is my repo on Codeberg, on which we are rewriting a Python code base to C: https://codeberg.org/MorsMortium/LBRY-GTK/

The CRewrite branch contains the rewritten files, but the bar still displays what is in the main branch.

Screenshots

No response

Originally created by @MorsMortium on GitHub (Dec 10, 2022). ### Feature Description It would be nice, if the bar displaying how many percent of the repo is what language, would display the currently selected branch, instead of main. Not sure if this is bug or feature. An example is my repo on Codeberg, on which we are rewriting a Python code base to C: https://codeberg.org/MorsMortium/LBRY-GTK/ The CRewrite branch contains the rewritten files, but the bar still displays what is in the main branch. ### Screenshots _No response_

GiteaMirror added the type/proposal label 2025-11-02 08:54:21 -06:00

GiteaMirror commented

2025-11-02 08:54:21 -06:00

@lafriks commented on GitHub (Dec 12, 2022):

That would be expensive as calculating must be done by reading all repository files and hard to keep in sync as there are no branch information stored in database

@lafriks commented on GitHub (Dec 12, 2022): That would be expensive as calculating must be done by reading all repository files and hard to keep in sync as there are no branch information stored in database

GiteaMirror commented

2025-11-02 08:54:21 -06:00

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

Not sure how this database looks, but there could be a small table, containing branch specific data. Then it would be the same update process, that's currently used, but with actual branch pushed to, instead of main. Though creating these tables, updating them, per push and per branch creation/deletion might be too much just for this feature.

@MorsMortium commented on GitHub (Dec 14, 2022): Not sure how this database looks, but there could be a small table, containing branch specific data. Then it would be the same update process, that's currently used, but with actual branch pushed to, instead of main. Though creating these tables, updating them, per push and per branch creation/deletion might be too much just for this feature.

GiteaMirror commented

2025-11-02 08:54:22 -06:00

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

Not sure how this database looks, but there could be a small table, containing branch specific data. Then it would be the same update process, that's currently used, but with actual branch pushed to, instead of main. Though creating these tables, updating them, per push and per branch creation/deletion might be too much just for this feature.

It depends how many branches does the repository have.

@lunny commented on GitHub (Dec 14, 2022): > Not sure how this database looks, but there could be a small table, containing branch specific data. Then it would be the same update process, that's currently used, but with actual branch pushed to, instead of main. Though creating these tables, updating them, per push and per branch creation/deletion might be too much just for this feature. It depends how many branches does the repository have.

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#9961