Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Important addendum to 4 that can throw someone their first time - Put the new test in a new file and don't commit it to the repo yet. You don't want it to disappear or conflict with old versions of the test file when bisect checks old commits.


I've always liked having regression tests somewhat isolated anyway, so this works well with that.


This is one annoying footgun. It would be great if git could ignore some special .bisect directory during the entire process. This way the script doesn’t need a load of ../..


Create a .bisect directory and stick a gitignore inside it that ignores the folder. Or, add .bisect/ to a global gitignore file.


You can checkout the bisect script commit in another directoy. Or use $git bisect run $(git show ...).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: