Users should always be able to dismiss their own PR approval or request-changes, but the option sometimes disappears

[AlanSl]

Select Topic Area

Bug

Body

It's not rare for a reviewer to approve a PR and then have a reason to un-approve it: for example, they might notice something they initially missed, or some team decision might have changed, or some other work might have made this work no longer valid.

Currently the process to dismiss an "approve" is, unintuitively, done from the "Changes approved" summary box at the bottom of the PR. Not only is this not necessarily an intuitive place to look, it isn't always available:

• if another step in a CI pipeline that is part of the PR checks fails, it seems the box does not show, preventing approvals from being dismissed. It's very counter-intuitive that a failure in CI should make it impossible for a reviewer to dismiss their own approval.
• if a parrallel change to the main branch caused merge conflicts to exist, those merge conflicts seem to cause the "Changes approved" box to disappear, again making it impossible for a reviewer to dismiss their own approve.

The option to dismiss an approve should always be present, and it should be in a stable, intuitive place. Ideally it should be an option next to every green tick and user chip indicating that you approved the PR, next to the "re-request review" (which some users already incorrectly believe dismisses approvals).

---

For example, here, there's no section summarising the reviews and approvals, so it's impossible for me to dismiss my approval:

Here's an example from the same repo where CI passed but a merge conflict has caused the "dismiss review" link to not show (this repo does not auto-dismiss reviews):

---

I think all of the above also applies to "Request changes" but I don't currently have a "request changes" I want to dismiss to test with.

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[imericxu]

Any updates? This is kind of ridiculous.