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

> I guess this is the difference, I expect the commit to represent a somewhat working version,

On a solo project I do the opposite: I make sure there is an error where I stopped last. Typically I put in in a call to the function that is needed next so i get a linker error.

6 months later when I go back to the project that link error tells me all I need to know about what comes next



How does that work out if you want to use `git bisect` to find regressions or similar things?


I dont do bisects on each individual branch. I'll bisect on master instead and find the offending merge.

From that point bisect is not needed.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: