3 ms·
I think it's fine if you squash it. I have no idea why they didn't squash it before pushing to GitHub though.
by IshKebab 1y ago
I think it's fine if you squash it. I have no idea why they didn't squash it before pushing to GitHub though.
- speedgoose 1y agoThey probably didn’t care. And having many small commits instead of a big squashed one can be useful when using git bisect for example.
- davedx 1y agoYeah. I have never in my entire career thought "there are too many commit messages" when doing code archeology, but I have sometimes thought "damn, this commit is huge"
- IshKebab 1y agoI have all the time. When git blame says "fix a typo" or when you look at a commit graph and see spaghetti.
- __david__ 1y agoI like `tig blame` for this. It has a key (comma, maybe?) that pops back to the file just before the change on the highlighted line so you can quickly work your way backwards through non-changes like you describe. It doesn’t deal with renames well, though.
- IshKebab 1y agoNot really because CI only needs to pass for the final commit so it's super unlikely that the intermediate ones work.
- tkfoss 1y agoThey squashed it before pushing to main.
- almostgotcaught 1y ago@Mogball Mogball enabled auto-merge (squash) 3 months ago @Mogball Mogball merged commit ade3d49 into main on Jul 9