3 ms·
Used it yesterday You train people/enforce in CI that all commits on `main` compile. People shouldn't not be committing broken code. Squash if they can't mana
by david_allison 2y ago
Used it yesterday
You train people/enforce in CI that all commits on `main` compile. People shouldn't not be committing broken code. Squash if they can't manage that.
1) You can `skip` a bad commit if it happens
2) You can branch and rebase a unit test into the history to use a scripted bisect run
- growse 2y agoI'm interested in #2 here - I've often struggled with writing a test to identify a bug, and then using that new test with bisect to find the commit where that test would first fail. Has this technique got a googlable name?
- david_allison 2y agoNo googleable name. I think the following is enough to explain the concept. It's not quite how I do things, but it's mostly right https://www.pauline-vos.nl/fix-bugs-%E2%9A%A1-fast-with-regression-tests-and-auto-bisect/ https://www.pauline-vos.nl/fix-bugs-%E2%9A%A1-fast-with-regr...
- growse 2y agoThanks- commit then rebase reorder is a simple but great idea!