Undo the revision to the description of issues/pull requests.

[CVFA1]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Other

Body

I think GitHub should have a button to easily revert edits to the description of issues or pull requests to a previous revision.

Yes, there is the option of simply copying the old content into a new one, but it’s not as easy as a ‘Revert’ button.

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

[mohammadrezwankhan]

GitHub already keeps an edit history for issue descriptions, but the current documented workflow is review-and-copy rather than a one-click rollback. The editing guide says the history is available unless the author or someone with write access removes it:

https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/editing-an-issue

For a description that was changed accidentally, click the edited indicator next to the current body, open the earlier revision, copy the desired text, and edit the current description back. That preserves the existing issue/PR timeline and avoids rewriting comments. gh issue edit can update the current title/body, but the CLI documentation does not expose a “restore revision” command.

The REST timeline API is still useful for auditing when an edit happened and who made it, but it is not documented as a revision-restore endpoint:

https://docs.github.com/en/rest/issues/timeline

A safe native feature would be Restore this revision with a preview and the same permission checks as editing. It should create a new edit event (not erase the current revision), retain the audit trail, and optionally require a confirmation when restoring someone else’s edit. That would give maintainers a reversible workflow without weakening the existing history controls.