57 questions in Git.
· Git
Choose between git reset --soft/--mixed/--hard, git revert, git commit --amend, and git restore based on whether the commit was pushed and whether you want to keep the changes.
· Git
Read Git's conflict markers, choose between manual edits and git mergetool, use --ours/--theirs strategically, and avoid the most common pitfalls (committing markers, wrong-side picks, repeated rebase conflicts).
· Git
Set your Git identity globally, per-repository, or conditionally per directory; sign commits with SSH or GPG so GitHub and GitLab show them as Verified.
· Git
Apply a specific commit from one branch to another with git cherry-pick: single commits, ranges, merge commits with -m, no-commit staging, conflict resolution, and the difference between cherry-pick and rebase --onto.
· Git
Amend the last commit's message, add forgotten files, fix author info, change the timestamp, and understand why amend rewrites the SHA — plus the rules that keep --amend safe on shared branches.
· Git
Practical guide to git stash: push/pop/apply/drop semantics, including untracked files and ignored files, partial stashes with --patch, and when a WIP commit or git worktree is the better tool.
· Git
Compare git merge and git rebase by what they do to history, when each is correct, the team rules that prevent broken pushes, and the half-dozen failure modes nobody warns you about.
· Git
Create and switch to a Git branch with git switch -c, set up upstream tracking, follow conventional naming, and avoid the common pitfalls around stale base branches and detached HEAD.
· Git
Best practices for using Git in teams: branching strategies, commit conventions, code review workflows, and common pitfalls to avoid.
· Git
Find the exact commit that introduced a bug using Git bisect binary search.