git-advanced-workflows

Git bisect finds bug-introducing commits by binary searching your history. You mark commits as good or bad, and Git automatically checks out intermediate revisions until it identifies the exact commit that introduced the regression.

Applying a hotfix across release branches is best done with git cherry-pick. You create the fix on a main branch, then cherry-pick the specific commit into each release branch to ensure synchronization without breaking existing workflows.

Git reflog records a history of all reference updates, including hard resets and deleted branches. By checking the reflog, you can find the hash of lost commits and use git checkout or git reset to restore your repository to a previous state.

Git worktrees are needed when you want to work on multiple branches simultaneously without stashing changes. They allow you to check out multiple branches into separate directories, enabling parallel development and testing on the same repository.

Yes, git rebase is used to clean up commit history by reordering, squashing, or editing commits. It rewrites your branch history to maintain a clean, linear progression before merging changes into your main branch.

To synchronize branches after history cleanup, you use git rebase or git merge to align your commits. This ensures all branches reflect the cleaned history and prevents conflicts during future integrations.