delete button on file changes on prs should become revert

[galnadjar]

🏷️ Discussion Type

Product Feedback

Body

there is no logical reason to have delete button on changes in prs
revert button should replace it completly,
if its new file revert anyways means not having it => delete it
if its existing file, it means revert all changes done in this file
its not really logical that we need to do git operation of revert/reset on a specific file
its fairly simple change that is a big quality of life game changer which i think is obvious to do, supported by my entire collegues
please consider this

[Himanshu-Singh11]

I agree that having a clearer “Revert” option would improve the PR review experience. For new files, reverting should simply remove the file from the PR. For existing files, it should restore that file to its original state before the PR changes.

A separate delete button can be confusing because reviewers may not always understand whether it is deleting the file from the repository or only removing the proposed change. A dedicated “Revert changes in this file” action would be more intuitive and safer, especially when reviewing large PRs.

[galnadjar]

i would say
if revert is reverting change in files it should just revert and also maybe have icon of undo
if revert is reverting change in files that didnt exist, it should have a garbage icon and maybe prompt u to "reverting changes in current file will result a deletion of it since it doesnt exist in origin" and u know what, may be even called delete file,
but if it exist in base branch it should just prompt u to revert the changes done within it

so to sumup , icons + validation of removal screen with the details should do that

[edenchazard]

I like this suggestion. There have been plenty of times I'd rather revert a file than outright delete it.

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