Hey everyone,<p>over the past two months I made it myself a challenge to write an ebook about rebasing in git and today I'm happy to launch a first version of it!<p>I see a lot of people struggling with having a fundamental understanding of how git works. Rebasing in Git is probably one of the most powerful features of the tool that can make everyone extremely productive when it comes to version control and working with peers on projects.<p>I've documented my progress at IndieHackers here: <a href="https://www.indiehackers.com/product/rebase-book" rel="nofollow">https://www.indiehackers.com/product/rebase-book</a><p>Will also write a post-mortem about how I've authored and published the book in just two months.<p>Feel free to follow me on twitter for updates: <a href="https://twitter.com/PascalPrecht" rel="nofollow">https://twitter.com/PascalPrecht</a>
Not to undermine author’s efforts, but I feel we as an industry took a wrong turn somewhere. An entire book on what essentially is a single Git command is just insane.
The thing is, git is a tool, it should be pretty easy to use. If someone has to write an entire book about rebasing then, in my opinion, there's something wrong.<p>I just push/pull/merge. I've never had any issues, a monkey could do it and would have to go out of their way to screw it all up.<p>"Noob! You don't understand how git works"... maybe true. I understand how source control should work. I have far more important things on my day-to-day plate then to dig into the internal workings of git. The branching setup described in the git-flow thing has been around far longer than git.