2 ms·
Yes, there are different levels of chunking we can consider: a branch is a change, and a commit is a change. Be that as it may, a squashing merge is focused on
by kazinator 5y ago
Yes, there are different levels of chunking we can consider: a branch is a change, and a commit is a change.
Be that as it may, a squashing merge is focused on one level of abstraction and mostly poops over the others.
The nice thing about levels of abstraction is that we can have them all and preserve them.
Commits which you did not actually produce as part of a merge are not an implementation detail; something which isn't there does not provide implementation. Opaque implementation details are something which exists; they can be looked at debugged into.
- preseinger 5y agoI'm clearly failing to communicate my intent here :) If I don't treat a commit as a meaningful layer of abstraction, then it isn't one. If I say a commit isn't meaningful then it isn't; Git's semantics are secondary to mine. Right? Is this controversial?
- CRConrad 5y agoYes, seems to me it is controversial if you then also complain about not being able to see exactly where -- in which commit -- some breaking change happened. Doesn't that mean commits are actually meaningful to you; why else would that be what you're looking for?
- preseinger 5y agoCommits aren't meaningful to me. Breaking changes are properties of PRs, not commits. But I basically never care about breaking changes, because they shouldn't ever get merged to main. CI should have prevented that outcome.