Copilot · GitHub Blog
Rendering major pull requests in the GitHub Copilot app
Compiled by KHAO Editorial — aggregated from 1 source. See llms.txt for citation guidance.
★ Tier-1 Source
Broad refactors and migrations often have to land as one change.
Key facts
- To see how far that goes, they opened the biggest pull request they could find: an open source one with 2,200 files, over a million changed lines, and more than 400 inline review comments
- Broad refactors and migrations often have to land as one change
- Stacked pull requests are a great way to split work into smaller changes, which makes reviews easier and helps teams ship with less risk
- That leaves you with a single pull request that can get large, and the review conversation causes it to grow
Summary
Stacked pull requests are a great way to split work into smaller changes, which makes reviews easier and helps teams ship with less risk. The review experience needs to remain fast and smooth even when the diff and its conversation are enormous. To see how far that goes, they opened the biggest pull request they could find: an open source one with 2,200 files, over a million changed lines, and more than 400 inline review comments. Rendering a large diff at speed is well-understood: virtualize the rows, keep the mounted DOM small, and lean on the fact that every row is a line of code at a known height. Comments are the hard part.