github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-19 14:42:41 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Paginate commits and changes on new pull request #2707

New Issue
Open
opened 2025-11-02 04:45:09 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2025-11-02 04:45:09 -06:00
Owner
Copy Link

Originally created by @vijfhoek on GitHub (Jan 4, 2019).

Currently, commits and changes on a new pull request are not paginated. I just opened a massive pull request with almost 300 commits, which took about half a minute to render in my browser.

Perhaps we should limit it to ~50 commits (or something) and add pagination to browse through the commits.

I understand it's a pretty rare event, but it'd be nice to have.

Originally created by @vijfhoek on GitHub (Jan 4, 2019). Currently, commits and changes on a new pull request are not paginated. I just opened a massive pull request with almost 300 commits, which took about half a minute to render in my browser. Perhaps we should limit it to ~50 commits (or something) and add pagination to browse through the commits. I understand it's a pretty rare event, but it'd be nice to have.
GiteaMirror added the type/proposaltype/enhancement labels 2025-11-02 04:45:09 -06:00
GiteaMirror commented 2025-11-02 04:45:09 -06:00
Author
Owner
Copy Link

@SebastianGode commented on GitHub (Dec 12, 2023):

@lunny Are there any news to that?

@SebastianGode commented on GitHub (Dec 12, 2023): @lunny Are there any news to that?
GiteaMirror commented 2025-11-02 04:45:09 -06:00
Author
Owner
Copy Link

@tischrei commented on GitHub (Dec 12, 2023):

We have also such issues, because we are using PRs with 300 comments+. Our page load takes 4-5 minutes which is way too long and takes 1 GB RAM and more. Could anyone have a look on this and maybe introduce some performance buff / pagination?

image

@tischrei commented on GitHub (Dec 12, 2023): We have also such issues, because we are using PRs with 300 comments+. Our page load takes 4-5 minutes which is way too long and takes 1 GB RAM and more. Could anyone have a look on this and maybe introduce some performance buff / pagination? ![image](https://github.com/go-gitea/gitea/assets/26574398/1a37e484-11cc-47b8-bec3-4acdd6148982)
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/enhancement 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#2707
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?