git-bisect is part of the git CM software. It is used to find which change broke something.
Questions tagged [git-bisect]
101 questions
1
vote
2 answers
Is `git reset --hard` required before mark the current commit as good or bad during bisect?
In my current workflow, I'm updating/rebasing an ancient patch to work against recent versions of a projetct.
In my current workflow, I use git bisect to find the latest commit which can be used to cleanly apply the patch.
To check if the patch can…
vinipsmaker
- 2,215
- 2
- 19
- 33
1
vote
1 answer
Algorithm to find when a set of git projects was broken?
Let's assume I have N git projects, which combined together define a release/ repository R.
When R pass a sanity test, T, we name it a good R and if it fails we name it a bad R.
I want to come up with a script, and in the future push it to google…
0x90
- 39,472
- 36
- 165
- 245
1
vote
2 answers
git bisect is stuck
I know that the tip of topic-branch-7 has a bug, and I know that the tip of master does not have the bug. I'd like to find out where the bug was introduced in topic-branch-7. So I've run the following:
git checkout topic-branch-7
# some testing to…
skiphoppy
- 97,646
- 72
- 174
- 218
1
vote
1 answer
Can I make git bisect display shortened commit SHAs?
Running git bisect generates output like this after each bisection:
Bisecting: 22 revisions left to test after this (roughly 5 steps)
[123fedacc728b985d4f8d010e2a69dcbdcbf3e8e] use binascii module for hex/binary conversions
Can I make it use…
Simon Whitaker
- 20,506
- 4
- 62
- 79
0
votes
1 answer
What does it mean for git bisect to produce a merge base which is both bad and good?
I've just performed a lengthy bisect, and received the following output from git:
The merge base ec879c71aa41065af101d1cce61966417e8d53c9 is bad.
This means the bug has been fixed between ec879c71aa41065af101d1cce61966417e8d53c9 and…
ash
- 5,139
- 2
- 27
- 39
0
votes
1 answer