Practise the standard verbs for triaging regressions with Git bisect.
0 / 5 completed
1 / 5
Fill in: 'We ___ a bisect session once a regression appears but the guilty commit isn't obvious.'
We 'run a bisect' — the standard, established Git collocation for starting the binary-search debugging process. The other options aren't the recognised term here.
2 / 5
Fill in: 'We ___ a known-good and a known-bad commit before bisect can start narrowing down the range.'
We 'mark' a commit — the standard, established Git collocation for tagging a reference point as good or bad. The other options aren't the recognised term here.
3 / 5
Fill in: 'A flaky test in the middle of the range can ___ a bisect session down entirely the wrong path.'
We say a flaky result will 'send' bisect the wrong way — the standard, natural collocation for a misleading signal. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ an automated script to bisect so each candidate commit gets tested without manual intervention.'
We 'use a script' — the standard, simple collocation for automating a repetitive step. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the offending commit once bisect narrows it down to a single, isolated change.'
We 'identify' a commit — the standard, simple collocation for pinpointing the exact cause. The other options are less idiomatic here.