Pull request page become so slow when pr is big #33663
Replies: 9 comments 5 replies
-
Same problem here. Is horrible. this should be high priority |
Beta Was this translation helpful? Give feedback.
-
I've been using the |
Beta Was this translation helpful? Give feedback.
-
Same here on Chrome. Switching to Firefox, and it's no longer an issue. Here's my tampermonkey script to remind me to use firefox instead. |
Beta Was this translation helpful? Give feedback.
-
Same here |
Beta Was this translation helpful? Give feedback.
-
This has gotten incredibly bad. |
Beta Was this translation helpful? Give feedback.
-
Above 50 files changed the UI becomes unusable. How about paging the results instead of loading more than the browser can handle? |
Beta Was this translation helpful? Give feedback.
-
Indeed, it is horribly slow |
Beta Was this translation helpful? Give feedback.
-
It is so bad, can't believe a company at GitHub's level is doing this |
Beta Was this translation helpful? Give feedback.
-
Commenting to get more traction on this. Using Chrome - PRs aren't even that big (~50-80 files, not too many lines per file) and slowness becomes unbearable. It really does sound like paging could help ? |
Beta Was this translation helpful? Give feedback.
-
My company used to make a big PR for major update. It's very difficult to review or check comment with code in Pull request page because it become too laggy to review in page.
I hope it become optimized.
Beta Was this translation helpful? Give feedback.
All reactions