5 ms·
I disagree with both of you :). Personally I prefer to squash to one commit per ticket but on a team level I don't care about a consistent way. I've found that
by mibollma 4y ago
I disagree with both of you :).
Personally I prefer to squash to one commit per ticket but on a team level I don't care about a consistent way.
I've found that the history rarely doesn't matter at all to me.
Finding out who modified a specific code section (git blame) is usually good enough.
- CBarkleyU 4y agoIn the hopes someone will see this: Why isnt this the standard? I've never been in the position of coordinating multiple engineers, but when I look at my colleagues code I never ever once cared about their individual commits. What am I missing?