[pinoy420]

Interesting

I have only worked on huge applications that take ages to spin up so bisect was never really an option.

> start doing something unrelated to the task I would change branch to that — if I ever had liberty to change priorities like that.

I have not tried git switch thank you

[kartoffelmos]

We try to have a clean-as-you-go policy. Try to improve bits and bobs while maintaining the code base as a whole. While (IMO) a one-liner here and there is fine, it can quickly spiral out of control.

I usually keep an improvements commit at the start of my branch which I `--amend` to while picking away at the task. If the commit gets too big I submit it separately, to be reviewed in isolation.

[Izkata]

> I have only worked on huge applications that take ages to spin up so bisect was never really an option.

That's the best time to use bisect, set up a script to automate the build and test for the specific thing you're looking for, then use "git bisect auto ./foo.sh" and go to lunch.