5 ms·
For rebasing specifically I often don’t make a temporary branch. I’ll use the reflog and reset to the commit hash if something gets messed up. Those “backup”
by avgcorrection 5y ago
For rebasing specifically I often don’t make a temporary branch. I’ll use the reflog and reset to the commit hash if something gets messed up.
Those “backup” branches really aren’t that for me. They’re just named commits which makes it easier to figure out where I was. But they are sometimes necessary since the reflog isn’t always nice and easy to read.
And pushing that branch to a remote? That’s unnecessary unless you want to delete the whole repo and clone it again in case you “mess it up”. Well, I guess that could be useful in a tutorial.
- lelandfe 5y agoBear in mind we’re teaching folks how to rebase - reflog can be an intimidating dive for a first blush discussion
- dvlsg 5y ago`git reset --hard ORIG_HEAD` is often enough to "undo" a rebase that went haywire. `git rebase --abort` can be helpful too, if you run into some unexpected merge conflicts along the way.