39 / 57 · 17 Git & Version Control · Bisect and Cherry-Pick← prev⊞ allnext →☰ Read as one page
5.9Combining Bisect and Cherry-Pick
A powerful QA workflow:
- Bisect to find the commit that introduced a regression
- Review the commit to understand the root cause
- Work with the developer to create a fix
- Cherry-pick the fix to the release branch for immediate deployment
- Merge the fix to develop for long-term integration
# Step 1: Find the regression
git bisect start HEAD v2.3.0
git bisect run npx playwright test tests/checkout.spec.ts
# Result: commit abc123f introduced the regression
# Step 2: Review
git show abc123f
# Step 3: Developer creates fix on develop (commit def456a)
# Step 4: Cherry-pick fix to release branch
git checkout release/2.4
git cherry-pick def456a
# Step 5: Verify the fix
npx playwright test tests/checkout.spec.ts