Get the latest tech news
I kind of like rebasing
People tend to get pretty passionate about Git workflows on different online forums. Some like to rebase, while others prefer to keep the disorganized records. Some dislike the extra merge commit, while others love to preserve all the historical artifacts. There’s merit to both sides of the discussion. That being said, I kind of like rebasing because I’m a messy committer who: Usually doesn’t care for keeping atomic commits1. Creates a lot of short commits with messages like “fix” or “wip”.
Prefers a linear history over a forked one so that git log --oneline --graph tells a nice story. Sure, a similar result can be emulated using git merge --squash feat_branch or GitHub’s squash-merge feature, but to me, rebasing feels cleaner. Protobuffed contracts TypeIs does what I thought TypeGuard would do in Python ETag and HTTP caching Crossing the CORS crossroad Dysfunctional options pattern in Go Einstellung effect Strategy pattern in Go Anemic stack traces in Go Retry function in Go Type assertion vs type switches in Go
Or read this on Hacker News