GitHub moves the merge box to the top of pull requests
GitHub New pull request overview page in public preview
GitHub has launched an opt-in public preview of a new pull request Overview page that pulls merge status and next actions to the top in a compact readiness summary. The redesigned merge box shows the same information in less than half the space, and new filters let you narrow to unresolved conversations or your own comments and sort newest-first. You can toggle back to the classic view anytime during the preview.
On a long pull request, checking what's blocking often means scrolling past dozens of comments and timeline events just to reach the merge box.
- capevace
We’ve been building our own Review Pipeline, including automated review guides, risk detection and much more.
There’s SO much to be done around Code Review, I’m very surprised GitHub isn’t doing more.
They have the reach already, they have years of real review data. And yet, the PR itself is not using any of the newly available methods for more efficient review.
Agents are hammering PRs out left and right, and yet here I am still staring at the raw diff of 35 PRs and end up being called the bottleneck.
- gz09
I wish they would instead focus on fixing the regressions with PRs first...
For example: There is a nasty bug that got introduced recently where you click "Merge when ready" but your chances of things actually going to the merge queue seem to be only at about 60-70%. When it happens the way you usually find out if things still aren't merged the next day.
Their support has acknowledged the issue to us over a month ago but no fix as of now.
- habosa
This is a major improvement and still not great. I made CodeApprove (https://codeapprove.com) 6+ years ago just because the PR page on GitHub is so bad and I felt the urge to make it better.
IMO the correct design is pretty simple:
- Everything on one page, information dense
- Focus on code and unresolved discussions, maybe CI checks
- Keyboard navigation
Graphite gets pretty close! But it's become cluttered over the years. CodeApprove is far from perfect too (it's been a while since I worked on the UX much) but I'd hope GitHub could do a little better.
- locallylinear
Idk, I just ask my agent what the status of the PR is in terms of failing checks, outstanding comments, etc.
But this seems fine
If anything I think the place to invest a better UX is on reviewing code, even “my” (agent’s) own code before I ask for a review. In a world where we’re moving away from IDEs, and using terminal apps or desktop apps to code, I often don’t even see the code until it’s on GitHub. But I still cling on to some semblance of needing to review, in particular what’s important.
And yes, me one year ago would be shocked at what I just said.
- johnnypangs
I don’t like that they reversed the the comment thread order but didn’t include a native way to include previews. Now instead of having to scroll to bottom to see the merge button. I have to scroll to the bottom to see the preview.
- verst
I've been using this for a few weeks but I don't quite like it. It's too many clicks to navigate to the PR discussion / comments for my liking.
- pscanf
I tried it, but I don't understand the fanfare when it's basically the same old UI + a couple of minor layout changes. It definitely doesn't address the needs of the AI dev workflows.
- ethin
I wish that instead of trying to make the UI look pretty GH would instead try to make the platform solid again