JackbyDev

I don’t know, the number of times I’ve needed to make two small changes in parallel is certainly non zero. The amount of times I’ve been mostly done with a feature and began a new one before a PR was totally merged is certainly non zero. Even then, some changes can make more sense if broken it into multiple commits (a moot point at most teams since squash and rebase seems to be the norm). You can keep a linear history and still have multiple commits in a branch, just commit (har har) to reading instead of merging.

Regardless, doing commit fixups and rewords are not necessarily rare. These commands are still super useful. Bear in mind that just because something isn’t useful to your workflow, git is used by many different people with many different types of workflows.

“N~, best I got bros”

Maybe, but I don’t really see them as competitors. They’re both monster raising, yeah, but that’s honestly where the similarities stop. That said, I haven’t played Legends or ZA (whatever they’re called) which both seem closer to what Palworld is (still very different though)