2 ms·
I want a clean merge history I can run git bisect against. The utility of git bisect is much diminished when the commit history is full of broken commits. It wo
by jerf 5y ago
I want a clean merge history I can run git bisect against. The utility of git bisect is much diminished when the commit history is full of broken commits. It works best when all the commits successfully run the test suite at the time, which is perhaps not the highest standard of "clean commit" we could ask for but my impression is that it puts it fairly high vs. the "commit everything" criterion.
- ilammy 5y ago> I want a clean merge history I can run git bisect against. "git bisect" supports "--first-parent" too.
- freewilly1040 5y agoAll of these arguments are of the flavor “git supports —-flag-1%-of-users-know so that works.” But there’s a nontrivial cost to teaching all of your users a non default workflow, which you have to pay for every new person that comes along.
- jerf 5y agoIt doesn't matter what git supports if I'm bisecting into history where the tests don't run cleanly on every commit. Now I don't know whether the test case I'm bisecting with is broken because it's revealing the bug or if it's broken because the commit is broken. git bisect is literally mathematically useless if you get even a single --good or --bad wrong.