I'm pretty sure all these use cases are covered by rebase and --interactive. My use of --onto was for unrelated history.
In your first example just pass the first hash to rebase it will select the same second argument because that is the first common ancestor.
Your second can us -i and then drop the commits you don't want, reorder, edit...
Yeah, you're not wrong. Maybe the examples should be moving to a completely different base?? Seemed like an easy to show how it worked.
I do think that is important, but then you'd have to pull in an unrelated but similar repo.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm pretty sure all these use cases are covered by rebase and --interactive. My use of --onto was for unrelated history.
In your first example just pass the first hash to rebase it will select the same second argument because that is the first common ancestor.
Your second can us -i and then drop the commits you don't want, reorder, edit...
Yeah, you're not wrong. Maybe the examples should be moving to a completely different base?? Seemed like an easy to show how it worked.
I do think that is important, but then you'd have to pull in an unrelated but similar repo.