473
History repeats itself
(lemmy.world)
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
OK. Query.
Rebase or merge into current?
I personally never rebase. It always seems to have some problem. I'm surely there's a place and time for rebasing but I've never seen it in action I guess.
I try to structure my commits in a way that minimizes their blast radius, which usually likes trying to reduce the number of files In touch per commit.
For example, my commit history would look like this:
And then as I continue working, all changes will be
git commit --fixup
ed to one of those two commit's hashes depending on where they occur.And when it's time to rebase in full, I can do a
git rebase master --interactive --autosquash
.This is the way! Small commits with descriptive commit names, then just fixup into a few feature commits. Makes rebase a breeze.