3 ms·

Martin, small commits interrupt flow, contain intermediary trains of thought that aren’t relevant, and decompose the entirety of the feature in to unrecognizabl

• nerdponx 3y ago
  But it's much easier to rebase, squash, and reorder lots of small commits than a few big ones.
  • juped 3y ago
    The experience of splitting in git could be made nicer in a few ways, but yeah.
• __MatrixMan__ 3y ago
  If you want a a wholistically meaningful thing to look at for the feature, look at the PR. When you're looking for a smoking gun commit, you want it as small as possible, otherwise it'll take longer to fix.
• juped 3y ago
  > interrupt flow sorta. this really varies strongly from person to person and i wouldn't generalize. but you can construct small commits after you're done with your work. > contain intermediary trains of thought that aren't relevant no. delete these, they should not be present in the final history. > decompose the [...] i don't know what this is supposed to mean.