5 ms·
The key here is to ensure each commit has a single purpose. Fix a bug, add a feature, refactor, etc. Rebase is fantastic for taking multiple commits that toge
by RKoutnik 11y ago
The key here is to ensure each commit has a single purpose. Fix a bug, add a feature, refactor, etc. Rebase is fantastic for taking multiple commits that together have a single purpose and squash 'em into a single, purposeful, commit. Pulling together commits that have multiple purposes results in the problems you've found - bisect loses its effectiveness.
"Atomic commits" are one of the topics I'll be covering in this series. Hope this helps!
- agumonkey 11y agogit's way to direct you toward surgically precise commits amazed me at first but now I am frustrated because versionning is almost part of design and I don't know how to blend the two. Maybe it's just a matter of time. But almost no commits have a single purpose, it's always scattered around the main goal, with sprinkles of side-effects.