Add configuration directive to limit number of files shown in repo #2657

New Issue

GiteaMirror · 2025-11-02T04:43:44-06:00

GiteaMirror commented

2025-11-02 04:43:44 -06:00

Originally created by @NoraCodes on GitHub (Dec 13, 2018).

Gitea version (or commit ref): 1.6.1
Git version: git version 2.17.1
Operating system: Ubuntu 18.04.1 LTS
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Description

I use Gitea to store, among other things, a remote backup of my GPG encrypted passwords (with the pass utility), which means I have over 200 files in the root of a repository. This is problematic, as I sometimes want to view the repo but rarely care about the whole list of files, and this page can take upwards of 600ms to run.

It would be very cool to have a config option to limit the number of files shown, perhaps with a button to click to show all files.

Originally created by @NoraCodes on GitHub (Dec 13, 2018).  - Gitea version (or commit ref): 1.6.1 - Git version: git version 2.17.1 - Operating system: Ubuntu 18.04.1 LTS - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant ## Description I use Gitea to store, among other things, a remote backup of my GPG encrypted passwords (with the `pass` utility), which means I have over 200 files in the root of a repository. This is problematic, as I sometimes want to view the repo but rarely care about the whole list of files, and this page can take upwards of 600ms to run. It would be very cool to have a config option to limit the number of files shown, perhaps with a button to click to show all files.

GiteaMirror added the issue/confirmed type/enhancement labels 2025-11-02 04:43:44 -06:00

GiteaMirror commented

2025-11-02 04:43:45 -06:00

@stale[bot] commented on GitHub (Feb 11, 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 11, 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:43:45 -06:00

@NoraCodes commented on GitHub (Feb 21, 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.

Why is this the procedure? The problem still occurs.

@NoraCodes commented on GitHub (Feb 21, 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. Why is this the procedure? The problem still occurs.

GiteaMirror commented

2025-11-02 04:43:45 -06:00

@iamdoubz commented on GitHub (Jul 20, 2020):

I would like this to be added as well. For me, I am doing a large ERP upgrade and need to compare Oracle package and package bodies. We currently have over 16,000 files per branch (dev, test, and prod) in the repo and it takes 2268ms for page load and 2034ms for template load. If we could have a configuration that limits to only loading oh let's say 50 files at a time, that would be fantastic.

Do I need to put in a separate ticket?

@iamdoubz commented on GitHub (Jul 20, 2020): I would like this to be added as well. For me, I am doing a large ERP upgrade and need to compare Oracle package and package bodies. We currently have over 16,000 files per branch (dev, test, and prod) in the repo and it takes 2268ms for page load and 2034ms for template load. If we could have a configuration that limits to only loading oh let's say 50 files at a time, that would be fantastic. Do I need to put in a separate ticket?

GiteaMirror referenced this issue

2025-11-02 12:12:42 -06:00

[PR #2657] [MERGED] Refactor duplicated code in repo handlers #16527

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