Introducing the Revert Button

I think it would be neat if GitHub detected and archived branches that are deleted or overwritten with force --push. I don&#x27;t know how feasible this is but it would make it more true that <i>when code is pushed to GitHub, it&#x27;s safe</i>.<p>Edit: what I have in mind is something like a Recycle Bin or Trash for deleted branches where you can restore a branch (with a different name, if needed) or delete it permanently. Not some esoteric git feature. I&#x27;d like if it were added to git (as an optional feature enabled in .git&#x2F;config), but I&#x27;d want it to work more like stash than a feature for searching for things that were left behind.

I&#x27;d like to see a &quot;Squash pull request&quot; button to avoid merge commits, clean up messy pull requests with WIP commits and changes to address review feedback, and keep master bisectable at every commit.

This will be a huge help for teams of larger developers who use Github.<p>It&#x27;s really easy for a branch to &quot;look okay&quot; at the unit level (generally covered by the commit status API) and then completely fail at the integration level.<p>Enabling quick reverts of bad code encourages people to make the &quot;right fix&quot; rather than trying to hotfix issues in an integration environment (which blocks the rest of the team and prevents other features from going out).

Kind of ironic how Github continues to make it less necessary for developers to actually learn git.

This is an awesome feature - not one you&#x27;ll use every day, but one that&#x27;s very convenient when you&#x27;ve made an oops.

This is great! But why is it only for PRs? Why not any arbitrary commit?