Seems like you found it, but for others: one of the easiest ways to get a PR's diff/patch is to just put .diff or .patch at the end of its URL. I use this all the time!

Random PR example, https://github.com/microsoft/vscode/pull/280106 has a diff at https://github.com/microsoft/vscode/pull/280106.diff

Another thing that surprises some is that GitHub's forks are actually just "magic" branches. I.e the commits on a fork exist in the original repo: https://github.com/microsoft/vscode/commit/8fc3d909ad0f90561...

▲

compiler-guy 5 hours ago | parent [-]

It’s bonkers to me that there isn’t a link to the plan patch from the page. Yes, it’s trivial to add a suffix once you know, but lots of people don’t—as evidenced by this thread.

Discoverability in UX seems to have completely died.

	▲	bayindirh 4 hours ago \| parent [-]
		> It’s bonkers to me that there isn’t a link to the plan patch from the page. It's yet another brick on the wall of the garden. That's left there for now, but for how long? IOW, It's deliberate. Plus, GitHub omits to add trivial features (e.g.: deleting projects, "add review" button, etc.) while porting their UI. It feels like they don't care anymore.