@JPDev@programming.dev to Programmer Humor@programming.dev • 8 months agoRebase Supremacyprogramming.devimagemessage-square229fedilinkarrow-up11.13Karrow-down122
arrow-up11.11Karrow-down1imageRebase Supremacyprogramming.dev@JPDev@programming.dev to Programmer Humor@programming.dev • 8 months agomessage-square229fedilink
minus-square@jjjalljs@ttrpg.networklinkfedilink2•8 months agoI don’t want to see a dozen commits of “ran isort” “forgot to commit this file lol” quality. Do you? Having the finished feature bundled into one commit is nice. I wouldn’t call it stupid at all.
minus-squareAtemulinkfedilink1•8 months agoNote that I didn’t say that you should never squash commits. You should do that but with the intention of producing a clearer history, not as a general rule eliminating any possibly useful history.
I don’t want to see a dozen commits of “ran isort” “forgot to commit this file lol” quality.
Do you?
Having the finished feature bundled into one commit is nice. I wouldn’t call it stupid at all.
Note that I didn’t say that you should never squash commits. You should do that but with the intention of producing a clearer history, not as a general rule eliminating any possibly useful history.