The Business of Bisecting - Pauline Vos

Automation

Learn how to quickly find the commit that introduced a regression or bug in your code using Git's bisect feature, including how to start and reset the process, mark commits as good or bad, and automate the process with scripts.

Key takeaways

Use git bisect to quickly find the commit that introduced a regression or bug in your code.
Start by running git bisect start and then mark a commit as good or bad.
Use git bisect run to run your test suite on the current commit and check if it passes or fails.
Use git bisect good or git bisect bad to mark the commit as good or bad.
Use git bisect reset to reset the bisect process and start over.
Use git bisect skip to skip a commit if it’s not relevant to the problem.
Keep your commits atomic and small to make bisecting easier.
Use git bisect log to see a log of all the commits you’ve marked as good or bad.
Use a script to automate the bisect process and make it more efficient.
Use git bisect reset to reset the bisect process and start over.
Use git bisect start to start a new bisect process.
Use git bisect good or git bisect bad to mark the commit as good or bad.
Use git bisect run to run your test suite on the current commit and check if it passes or fails.
Use git bisect skip to skip a commit if it’s not relevant to the problem.
Keep your commits atomic and small to make bisecting easier.
Use git bisect log to see a log of all the commits you’ve marked as good or bad.
Use a script to automate the bisect process and make it more efficient.

The Business of Bisecting - Pauline Vos

More talks