git-advanced

To recover a branch after an accidental git reset --hard, use the git reflog to locate the lost commit hash and run git reset --hard <hash> to restore your branch to its previous state.

Git bisect uses a binary search algorithm across your commit history, requiring you to mark known good and bad commits so it can automatically checkout intermediate commits to pinpoint the exact one that introduced the regression.

Git submodules maintain dependency repositories as separate nested pointers within the parent repository, while git subtrees merge the dependency commits directly into your main project history, simplifying cloning but increasing repository size.

To clean up commit history, initiate an interactive rebase using git rebase -i and mark target commits as squash or fixup to combine multiple commits into a single, cleaner commit before force-pushing to your remote branch.

Git worktrees should be used when you need to work on multiple branches simultaneously, allowing you to checkout separate branches into different directories while sharing a single underlying .git directory to save disk space and cloning time.

Optimize git performance for large repositories by utilizing partial clones to download only necessary objects, enabling commit graphs for faster log traversals, and using sparse checkout to limit your working directory to only the required file paths.