Git flashcards, generated for you.

Creates a new .git directory in the current folder, initializing a local Git repository. Run once per project.

Working directory = your files on disk. Staging area (index) = changes marked for commit via `git add`. Repository = committed history in .git folder.

`git add .` stages all modified/new files in the current directory and subdirectories. `git add <file>` stages only the specified file. Both ignore deleted files unless you use `git add -A`.

Creates a snapshot of staged changes with the given message. The commit is permanent in local repo history. `-m` flag allows inline message; omitting it opens an editor.

Use `git reset HEAD <file>` (or `git restore --staged <file>` in Git 2.23+). Removes file from staging area but keeps changes in working directory.

`git checkout <branch>` switches branches but also checks out files, risking accidental overwrites. `git switch <branch>` (Git 2.23+) is safer and clearer. `git checkout` is overloaded for both branches and file recovery.

Merges another branch into current branch. Conflicts occur when both branches modify the same lines differently. Git marks conflicts with `<<<<<<<`, `=======`, `>>>>>>>` markers; you must manually resolve and re-commit.

`git merge` creates a merge commit, preserving both branch histories. `git rebase` replays commits on top of another branch, creating a linear history. Rebase rewrites history (avoid on public branches); merge is safer for shared code.

Uploads local commits to remote branch. Gotcha: if remote has newer commits, push fails. Use `git pull` first to sync, or `git push -f` to force (destructive—avoid on shared branches).

Occurs when checking out a commit hash instead of a branch; you're not on any branch. Changes here are orphaned if you switch away. Recover by `git switch -c <new-branch>` to save work, or `git reset --hard <safe-commit>` to discard.