-
Notifications
You must be signed in to change notification settings - Fork 170
[README] Add rebasing example #855
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
de4afb1
to
473267b
Compare
Excellent, thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don’t use this approach for cleaning up my git history. I follow the steps in #783 (comment). Squashing using interactive rebase sometimes leads to messing up of git history so I do it only when its outcome is predictable for me.
Yep. Maybe we can add another line here, mentioning: "create a backup branch before doing this interactive rebase." |
We should put both approaches there, I use both. @czgdp1807's approach is what I use for a complicated history with lots of merges, since a rebase will give me conflicts, but the |
473267b
to
cf99243
Compare
cf99243
to
2e2fc2c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a good start, it has all the information. I think the presentation can be more polished, but we can improve upon it with subsequent PRs I think.
No description provided.