Live data from Hacker News

Oh shit, git: Getting myself out of bad situations

ohshitgit.com

1–10 of 520 posts

Re: Oh shit, git: Getting myself out of bad situations

#5

If this is a guide for beginners, there should be (more?) warnings not to do history rewriting operations on commits that have already pushed.

Seems they agree:

> This site is not intended to be an exhaustive reference, nor is it a beginner's tutorial.

Re: Oh shit, git: Getting myself out of bad situations

#6

If this is a guide for beginners, there should be (more?) warnings not to do history rewriting operations on commits that have already pushed.

If you read to the bottom:

> Disclaimer: I am not, nor do I even remotely claim to be, an expert at git. This site is not intended to be an exhaustive reference, nor is it a beginner's tutorial. And yes, there are other ways to do these same things with more theoretical purity or whatever, but I've come to these steps through trial and error and lots of swearing and table flipping, and I had this crazy idea to share them with a healthy dose of levity and profanity. Take it or leave it as you will!

Re: Oh shit, git: Getting myself out of bad situations

#7

If this is a guide for beginners, there should be (more?) warnings not to do history rewriting operations on commits that have already pushed.

From the disclaimer at the bottom:

> This site is not intended to be an exhaustive reference, nor is it a beginner's tutorial.

Re: Oh shit, git: Getting myself out of bad situations

#10

If this is a guide for beginners, there should be (more?) warnings not to do history rewriting operations on commits that have already pushed.

Why is recovering from an upstream rebase considered more problematic than recovering from merge conflicts?
Post reply on HN