A much-needed refresh of the repository pull requests page landed in public preview this week: https://lnkd.in/gzmhfFCz It's very much in line with the rework we did on github.com/pulls earlier this year. We've all got a deluge of PRs these days, so we're working to make them easier to manage. Queries got more capable: you can combine filters with AND and OR, nest them, and get content assist as you type so you don't have to remember the syntax. And the page itself got reworked, with a sidebar for the filters people use most, a compact mode that fits more on screen, and check status, stack indicators, and unread updates inline. Try it out and give us feedback! #DeveloperTools #SoftwareEngineering
content assist on the filter syntax is the bit i'll actually notice, i've been guessing at that query from memory for years
Faisal Feroz
1d
Better filtering on PRs sounds small but it directly affects review velocity, which is something leadership often underestimates. When a team is drowning in a PR backlog, the bottleneck is usually not code quality, it is finding the right PR to review at the right time. I would be curious whether GitHub also improved the API around these filters, because that is what lets engineering teams build their own dashboards for review SLAs instead of relying on the UI alone.
I think the filters side menu should have been on the right side of the screen. It’s too far away from the assignee filter, which is the second rightmost item on the top bar, and also the actual assignee avatar. I find that it’s still easier to filter by my name the old way(of course my username is an A so I am at the top of the alphabetical list 😉
A small but high-leverage improvement for pull-request triage is making saved filters composable and shareable. Teams can standardize review queues without taking away each developer's personal view.
Justin Young
1d
Nice! Love to see it
The new filter and inline update experience looks like a solid improvement. 🚀 Making complex PR workflows easier to manage is definitely a win for developers! 👏
I think just a fresh UI isn't what is needed here, take a look at PHP Symfony where they experiment with disallow pull request, because LLMs can write the code anyway and they want better issues with deeper information of the problem, and on the other hand PHP Laravel closes the issues on github, so that users need to show there issue / or first fix via code in a pull requests because the LLMs can provide the needed information better and code is often more readable than a issue where the user don't know what version he is even using. So something is changing currently and that's not just the UI of this workflows.