تطوير تحسين

[ywsfnra-boopasdf123]

so, i have a bug in my dev branch but i don't have that in staging, i

wanna use git bisect inorder to find out which change introduced the bug, can't figure out how to do it in lazygit__

[leenlbma]

Lazygit has built-in bisect support — it's in the Commits panel, key b ("View bisect options", see docs/keybindings and the "Bisect" section of the README).

Steps for your case (bug exists on dev, not on staging):

1. Check out dev (Branches panel → select dev → space).
2. Go to the Commits panel (4, or click it).
3. Select the newest commit (HEAD, it has the bug), press b → choose "Mark … as bad (start bisect)".
4. Move to a commit you know is good — e.g. the commit that staging points to / the last commit shared with staging — press b → mark as good.
   • Tip: if that commit isn't easy to find in the list, you can get it with git merge-base dev staging and search the commit list with /.
5. Lazygit now checks out a commit in the middle and marks it in the list. Build/test it, then press b again and pick good, bad, or skip (if you can't test that commit).
6. Repeat until lazygit shows "Bisect complete! The following commit introduced the change: …". It then asks whether to reset bisect — answer yes (or later b → Reset bisect) to go back to your branch.

Via b → "Choose bisect terms" you can also use custom terms (e.g. old/new) if you're looking for when a behaviour changed rather than a bug.