3 ms·
This seems super useful- it matches my team's workflow, I'll def suggest we try it. Squash merge ftw
by teen 10y ago
This seems super useful- it matches my team's workflow, I'll def suggest we try it. Squash merge ftw
- DannyBee 10y agoI'm really curious about it. One of the purported reasons - "it makes git blame more useful", is pretty silly, unless you never have anyone fixing typos or reformatting code or whatever. git blame is already an approximation (because git, and well, everything, does not record what you did for real, only the smallest set of binary delta instructions you must execute to produce file version 2 from file version 1). So this is essentially is "this one git command sucks, so we are going to destroy all of history to make it's output slightly better in a few cases", instead of "hey, we are going to produce a version of blame that identifies the kind of info we care about"
- juped 10y ago>yfw you type `git blame --first-parent`