Introducing the Revert Button
github.com
Introducing the Revert Button
1–10 of 20 posts
Re: Introducing the Revert Button
#2This will be a huge help for teams of larger developers who use Github.
It's really easy for a branch to "look okay" at the unit level (generally covered by the commit status API) and then completely fail at the integration level.
Enabling quick reverts of bad code encourages people to make the "right fix" rather than trying to hotfix issues in an integration environment (which blocks the rest of the team and prevents other features from going out).
Re: Introducing the Revert Button
#3This is an awesome feature - not one you'll use every day, but one that's very convenient when you've made an oops.
Re: Introducing the Revert Button
#4Kind of ironic how Github continues to make it less necessary for developers to actually learn git.
Re: Introducing the Revert Button
#5I think it would be neat if GitHub detected and archived branches that are deleted or overwritten with force --push. I don't know how feasible this is but it would make it more true that when code is pushed to GitHub, it's safe.
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'd like if it were added to git (as an optional feature enabled in .git/config), but I'd want it to work more like stash than a feature for searching for things that were left behind.
Re: Introducing the Revert Button
#6Kind of ironic how Github continues to make it less necessary for developers to actually learn git.
And I personally couldn't be happier; most of the projects I'm involved with use Mercurial. So to me, git's interface is difficult to understand and foreign despite my own efforts to try to lean it.
GitHub and SourceTree combined have taken all the pain way from me using git.
Re: Introducing the Revert Button
#7Kind of ironic how Github continues to make it less necessary for developers to actually learn git.
Why would it not be their goal to abstract away the pain? Sure, you still have the power of git available to you, but not everyone who uses Github may want to learn git. They may simply be looking for versioning of their assets (images, geojson, etc).
Re: Introducing the Revert Button
#8I think it would be neat if GitHub detected and archived branches that are deleted or overwritten with force --push. I don't know how feasible this is but it would make it more true that when code is pushed to GitHub, it's safe . 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 e…
In a way that's already true, since the commits are still there (and included when you clone). They're just not discoverable.
It would be neat though if GitHub added some UI magic to recover dangling commits, possibly using the knowledge of which branches previously pointed to them and/or push -f operations.
Re: Introducing the Revert Button
#9I think it would be neat if GitHub detected and archived branches that are deleted or overwritten with force --push. I don't know how feasible this is but it would make it more true that when code is pushed to GitHub, it's safe . 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 e…
I think that (and correct me if I'm wrong) what you're really asking for is for the reflog to be exposed in some way.
Certainly I've force pushed before when I didn't mean to. When I went asking where the reflog was they (politely) offered to dig into my repo and give me a copy of my reflog. But I would have preferred if this was something that I could see easily myself.
Re: Introducing the Revert Button
#10I think it would be neat if GitHub detected and archived branches that are deleted or overwritten with force --push. I don't know how feasible this is but it would make it more true that when code is pushed to GitHub, it's safe . 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 e…
In a way that's already true, since the commits are still there (and included when you clone). They're just not discoverable. It would be neat though if GitHub added some UI magic to recover dangling commits, possibly using the knowledge of which branches previously pointed to them and/or push -f operations.
Aren't these part of what gets cleaned up by git gc?