-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] Pull requests: Lazy loading for diffs #6380
Comments
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. |
This would be a great feature to work on for |
Fixed in #16829? |
I'm trying it out but it's not working for me: https://try.gitea.io/jpraet-org/test-repo/pulls/1/files |
@jpraet please open new issues instead of commenting on old ones and give us logs for what went wrong. |
I cannot reproduce this locally therefore I need the logs. |
I'll open another ticket, but in the meantime, here's the log output when reproducing it locally:
I don't think the "Unable to open checker" error is the actual problem, as I also see that error when just opening the files tab on the PR. That one seems like a non-blocking error (that maybe should be looked into nonetheless?). |
What version of git do you have? |
damn I misread the git documentation - it looks like skip-to only appeared in git 2.31!! |
Bug report created: #17731 I'm using quite an old git version 2.18 on this machine. try.gitea.io is also on an older version then? |
Gitea: 1.7
Current situation:
If the amount of changed files reached a specific count, gitea shows the message that more files changed.
It is not possible to which files are affected.
This behaviour may a result of performance and memory issues.
Idea:
If the amount of files reach a specific count, all affected files are displayed collapsed. The user had to click on a specific file to see the difference.
The text was updated successfully, but these errors were encountered: