4 ms·
> are to make debugging tools such as `git log`, `git blame`, and `git bisect` more useful. *actually work. No point using `git bisect` if you switch to a com
by a10c 2y ago
> are to make debugging tools such as `git log`, `git blame`, and `git bisect` more useful.
*actually work.
No point using `git bisect` if you switch to a commit that literally doesn't even compile.
- maleldil 2y agoIf you have a commit that doesn't compile, it should have been squashed into another commit before merging the PR. Every commit should be in a valid state. I'm not talking about a full squash merge, just `git rebase -i` to make sure the history makes sense. The final branch history doesn't have to be the same as your development one.