Really really miss Azure Dev Ops PR functionality #144961
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
We recently migrated to github from Azure Dev Ops to be more in line with our broader organization. The entire team has found the pull request review experience in github to be extremely frustrating in comparison to ADO. It was so easy to see who was assigned to review PRs right in the PR list. You had filters to look at your active vs your reviewed PRs. If someone commits a change to a PR you have reviewed, ADO automatically reset your review status (as opposed to having to hit the request button in the reviewers list in github). There are many other little friction points that all feel like a piling up of papercuts to become a real point of frustration. We made the move for better integration with things like sonarqube code scans (which has been a good thing). We feel like the PR review experience has been a step in the wrong direction, but at least we got other benefits.
Beta Was this translation helpful? Give feedback.
All reactions