Git Commands Flashcards: Everyday Workflow, Branching & Recovery

Question 1

Initialize the current directory as a Git repository.

Accepted Answer

git init creates the repository metadata in the current directory.

git init

It doesn't add or commit the existing files.

Question 2

Set the commit email for only the current repository.

Accepted Answer

git config user.email dev@example.com sets a repository-local value.

git config user.email dev@example.com

Omitting --global keeps other repositories unchanged.

Question 3

Open the full manual for git status.

Accepted Answer

git help status opens the command's manual.

git help status

Use git status -h when you only need the short option summary in the terminal.

Question 4

Copy ../origin.git into a new local directory named project.

Accepted Answer

git clone ../origin.git project creates the local clone in project.

git clone ../origin.git project

The clone normally configures the source as the origin remote.

Question 5

Show tracked changes that haven't been staged.

Accepted Answer

git diff shows the working-tree changes relative to the index.

git diff

New untracked files don't appear until Git knows about them.

Question 6

Stage notes.txt for the next commit.

Accepted Answer

git add notes.txt copies the path's current content into the index.

git add notes.txt

Later edits to the file stay unstaged until you add them too.

Question 7

Inspect which changes are staged, unstaged, or untracked.

Accepted Answer

git status compares the working tree and index with HEAD.

git status

It reads repository state; it doesn't modify files or history.

Question 8

Record the staged snapshot with the message Add notes.

Accepted Answer

git commit -m "Add notes" creates a commit from the index.

git commit -m "Add notes"

Unstaged changes aren't included.

Question 9

Delete the tracked file obsolete.txt and stage that deletion.

Accepted Answer

git rm obsolete.txt removes the file and stages the removal.

git rm obsolete.txt

Commit afterward to record the deletion in history.

Question 10

Rename tracked old-name.txt to notes.txt and stage the change.

Accepted Answer

git mv old-name.txt notes.txt moves the path and updates the index.

git mv old-name.txt notes.txt

Git records snapshots, so it detects the rename from the resulting content when useful.

Question 11

List local branches and show which one is current.

Accepted Answer

git branch lists local branches and marks the current one with *.

git branch

It doesn't switch branches.

Question 12

Switch the working tree to the existing branch feature/login.

Accepted Answer

git switch feature/login switches to that branch.

git switch feature/login

Git updates the index and working tree, and refuses if the switch would overwrite local work. Older instructions often use git checkout for branch switching; switch states the intent more clearly.

Question 13

Show every configured remote with its fetch and push URL.

Accepted Answer

git remote -v lists remote names and URLs.

git remote -v

A remote name such as origin is a local shortcut, not a special server type.

Question 14

Read a compact one-line commit history.

Accepted Answer

git log --oneline prints one abbreviated entry per commit.

git log --oneline

The newest reachable commit appears first.

Question 15

Discard unstaged edits to tracked notes.txt.

Accepted Answer

git restore notes.txt replaces the working-tree file with the indexed version.

git restore notes.txt

This is destructive for those unstaged edits. Check git diff -- notes.txt first when unsure.

Question 16

Clone ../origin.git while naming the local directory sandbox.

Accepted Answer

git clone ../origin.git sandbox separates the source location from the local directory name.

git clone ../origin.git sandbox

Run it from the parent directory where sandbox should be created.

Question 17

Read the effective commit email in the current repository.

Accepted Answer

git config --get user.email prints the selected configuration value.

git config --get user.email

Repository-local configuration overrides a global value.

Question 18

Get a compact status that still shows branch information.

Accepted Answer

git status --short --branch prints the branch line plus two-column path states.

git status --short --branch

The left column describes the index; the right column describes the working tree.

Question 19

Review what is staged for the next commit.

Accepted Answer

git diff --staged compares the index with HEAD.

git diff --staged

--cached is the common equivalent spelling.

Question 20

Interactively stage selected hunks from notes.txt.

Accepted Answer

git add -p notes.txt lets you accept or reject each patch hunk.

git add -p notes.txt

This is useful when one file contains changes for more than one commit.

Question 21

Open the configured editor to write a commit message for the staged snapshot.

Accepted Answer

git commit opens the commit-message editor.

git commit

Git still commits only the staged content.

Question 22

Stop tracking local.env but keep the file in the working tree.

Accepted Answer

git rm --cached local.env stages removal from the index without deleting the local file.

git rm --cached local.env

Add the path to an ignore rule if it shouldn't be staged again.

Question 23

Create feature/login at the current commit without switching to it.

Accepted Answer

git branch feature/login creates the branch reference.

git branch feature/login

Use git switch -c feature/login when you want to create and switch in one step.

Question 24

Add ../upstream.git as a remote named upstream.

Accepted Answer

git remote add upstream ../upstream.git stores that remote configuration.

git remote add upstream ../upstream.git

It doesn't fetch any refs until you run git fetch upstream.

Question 25

View a compact decorated commit graph across all local refs.

Accepted Answer

git log --oneline --graph --decorate --all combines history, topology, and ref names.

git log --oneline --graph --decorate --all

It is a read-only way to understand how branches relate.

Question 26

Inspect the current commit's metadata and patch.

Accepted Answer

git show HEAD displays the commit and its changes.

git show HEAD

Replace HEAD with another revision when needed.

Question 27

Create feature/search at the current commit and switch to it.

Accepted Answer

git switch -c feature/search creates and checks out the branch.

git switch -c feature/search

New commits now advance feature/search.

Question 28

List the paths currently known to the index.

Accepted Answer

git ls-files prints tracked and staged paths.

git ls-files

It is more precise than a filesystem listing when you need Git's view.

Question 29

Refresh remote-tracking refs from origin without integrating them.

Accepted Answer

git fetch origin downloads objects and updates origin/* refs.

git fetch origin

Your current branch and working tree stay in place.

Question 30

Unstage notes.txt while keeping its working-tree edits.

Accepted Answer

git restore --staged notes.txt restores the index entry from HEAD by default.

git restore --staged notes.txt

The file's edited content remains in the working tree.

Question 31

Temporarily store tracked work with the label WIP login.

Accepted Answer

git stash push -m "WIP login" saves tracked staged and unstaged changes, then cleans them from the worktree.

git stash push -m "WIP login"

Untracked files stay put unless you add -u.

Question 32

Check how the current branch differs from its configured upstream.

Accepted Answer

git status --branch reports ahead, behind, or diverged state when an upstream exists.

git status --branch

It doesn't contact the remote, so fetch first when freshness matters.

Question 33

Compare the snapshots at main and feature/login.

Accepted Answer

git diff main feature/login shows changes needed to turn the first tree into the second.

git diff main feature/login

This compares the two named tips, not their merge base.

Question 34

Stage all additions, modifications, and deletions in the current repository.

Accepted Answer

git add -A updates the index for every path in scope.

git add -A

Review git diff --staged before committing a broad change.

Question 35

Replace the current local commit with a corrected snapshot but keep its message.

Accepted Answer

git commit --amend --no-edit creates a replacement commit from the current index.

git commit --amend --no-edit

Amending rewrites the commit ID. Avoid it after sharing the commit unless the team expects a history update.

Question 36

Rename the current branch to feature/auth.

Accepted Answer

git branch -m feature/auth renames the checked-out branch.

git branch -m feature/auth

If the old name was already pushed, coordinate the remote rename separately.

Question 37

Return to the branch you were on immediately before this one.

Accepted Answer

git switch - switches to the previously checked-out branch.

git switch -

It is handy for moving between two branches.

Question 38

Integrate feature/login into the current branch.

Accepted Answer

git merge feature/login joins the named branch into the current branch.

git merge feature/login

The result may be a fast-forward, merge commit, or conflict, depending on history and options.

Question 39

Fetch only the main branch from origin.

Accepted Answer

git fetch origin main downloads that branch and records the fetched tip in FETCH_HEAD.

git fetch origin main

It doesn't merge or move your current branch.

Question 40

Update the current branch only when the remote change can fast-forward it.

Accepted Answer

git pull --ff-only fetches, then refuses to create a merge commit or rebase.

git pull --ff-only

A refusal leaves the divergent histories for you to inspect.

Question 41

Push the current branch feature/login to origin.

Accepted Answer

git push origin feature/login updates the same-named remote branch.

git push origin feature/login

It doesn't configure an upstream unless your settings do that automatically.

Question 42

Read commits that changed notes.txt.

Accepted Answer

git log -- notes.txt limits history to commits affecting that path.

git log -- notes.txt

The -- separates revisions and options from the path.

Question 43

Print notes.txt exactly as it exists in HEAD without switching commits.

Accepted Answer

git show HEAD:notes.txt reads the blob at that revision and path.

git show HEAD:notes.txt

This doesn't modify the working-tree file.

Question 44

Search tracked working-tree files for the text TODO, including unstaged edits.

Accepted Answer

git grep TODO searches tracked files in the working tree, including their unstaged content.

git grep TODO

It skips untracked files by default.

Question 45

Show the commit and author associated with each line of notes.txt.

Accepted Answer

git blame notes.txt annotates each line with its last recorded change.

git blame notes.txt

Use it as a history lead, not as proof that one person owns the current behavior.

Question 46

Move the current branch back one commit while keeping the changes unstaged.

Accepted Answer

git reset HEAD~1 performs the default mixed reset.

git reset HEAD~1

It rewrites the local branch tip but leaves the changed files in the working tree.

Question 47

Stash tracked and untracked work together with the label WIP search.

Accepted Answer

git stash push -u -m "WIP search" includes untracked files.

git stash push -u -m "WIP search"

Ignored files still stay out unless you deliberately use the stronger --all option.

Question 48

List local tags whose names start with v1..

Accepted Answer

git tag --list "v1.*" filters the local tag names.

git tag --list "v1.*"

Listing tags doesn't contact a remote.

Question 49

Resolve HEAD to its full object ID.

Accepted Answer

git rev-parse HEAD prints the object name selected by the revision.

git rev-parse HEAD

This is useful in scripts that need an exact commit ID.

Question 50

Review prose edits as changed words instead of whole lines.

Accepted Answer

git diff --word-diff highlights inline word-level changes.

git diff --word-diff

It changes the display only; repository state stays untouched.

Question 51

Integrate feature/login only if the current branch can fast-forward.

Accepted Answer

git merge --ff-only feature/login refuses histories that require a merge commit.

git merge --ff-only feature/login

The refusal is a safety check, not a partial merge.

Question 52

Fetch origin and remove remote-tracking refs that the remote no longer has.

Accepted Answer

git fetch --prune origin refreshes refs and prunes stale origin/* names.

git fetch --prune origin

It doesn't delete local branches.

Question 53

List commits reachable from feature/login but not from main.

Accepted Answer

git log main..feature/login --oneline shows that one-sided revision range.

git log main..feature/login --oneline

The order around .. matters.

Question 54

Replace working-tree notes.txt with its version from HEAD~1.

Accepted Answer

git restore --source=HEAD~1 notes.txt copies the older blob into the working tree.

git restore --source=HEAD~1 notes.txt

This overwrites current unstaged edits to notes.txt. Diff, copy, or otherwise protect wanted edits first; then review and stage the restored version if you want to keep it.

Question 55

Create branch hotfix in an additional working tree at ../hotfix.

Accepted Answer

git worktree add ../hotfix -b hotfix creates the branch and checks it out there.

git worktree add ../hotfix -b hotfix

The original working tree stays on its current branch.

Question 56

Push feature/login and configure origin/feature/login as its upstream.

Accepted Answer

git push -u origin feature/login pushes the branch and records upstream tracking.

git push -u origin feature/login

Later git status, git pull, and git push can use that relationship.

Question 57

Follow likely moved or copied lines while blaming notes.txt.

Accepted Answer

git blame -M -C notes.txt adds move and copy detection heuristics.

git blame -M -C notes.txt

The result is still a clue for investigation, not an ownership verdict.

Question 58

Replay the current branch's local commits on top of main.

Accepted Answer

git rebase main rewrites those commits onto the new base.

git rebase main

Use it on unshared work, or coordinate before rewriting commits other people may use.

Question 59

Move the branch back one commit while keeping all reverted changes staged.

Accepted Answer

git reset --soft HEAD~1 moves HEAD but leaves the index and working tree intact.

git reset --soft HEAD~1

This rewrites the local branch tip and is best kept to unshared history.

Question 60

Create an annotated release tag v1.0.0 at the current commit.

Accepted Answer

git tag -a v1.0.0 -m "Release 1.0.0" creates a tag object with a message.

git tag -a v1.0.0 -m "Release 1.0.0"

Tags aren't pushed automatically unless you push them explicitly.

Question 61

Start a regression search with HEAD known bad and HEAD~4 known good.

Accepted Answer

git bisect start, followed by bad and good boundaries, begins binary search through the range.

git bisect start
git bisect bad HEAD
git bisect good HEAD~4

Git checks out a midpoint for you to test.

Question 62

Fetch the upstream branch, then replay local commits on top of it.

Accepted Answer

git pull --rebase combines fetch with a rebase-based integration.

git pull --rebase

It rewrites local commits, so inspect the branch and keep shared-history expectations in mind.

Question 63

Commit the staged update as Update notes while leaving unstaged edits out.

Accepted Answer

git commit -m "Update notes" records the index, not every working-tree edit.

git commit -m "Update notes"

Review both git diff --staged and git diff when the split matters.

Question 64

Undo the current non-merge commit with a new commit instead of moving the branch backward.

Accepted Answer

git revert HEAD applies the inverse of the current non-merge commit and records it as a new commit. git revert HEAD For a merge commit, inspect its parents and use the mainline form taught later: git revert -m

. Revert preserves shared history, which usually makes it safer than reset for published commits.

Tietoja tästä pakasta

What this deck practices

Tämän pakan kortit

Kortti 1

Kortti 2

Kortti 3

Kortti 4

Kortti 5

Kortti 6

Kortti 7

Kortti 8

Kortti 9

Kortti 10

Kortti 11

Kortti 12

Kortti 13

Kortti 14

Kortti 15

Kortti 16

Kortti 17

Kortti 18

Kortti 19

Kortti 20

Kortti 21

Kortti 22

Kortti 23

Kortti 24

Kortti 25

Kortti 26

Kortti 27

Kortti 28

Kortti 29

Kortti 30

Kortti 31

Kortti 32

Kortti 33

Kortti 34

Kortti 35

Kortti 36

Kortti 37

Kortti 38

Kortti 39

Kortti 40

Kortti 41

Kortti 42

Kortti 43

Kortti 44

Kortti 45

Kortti 46

Kortti 47

Kortti 48

Kortti 49

Kortti 50

Kortti 51

Kortti 52

Kortti 53

Kortti 54

Kortti 55

Kortti 56

Kortti 57

Kortti 58

Kortti 59

Kortti 60

Kortti 61

Kortti 62

Kortti 63

Kortti 64

Kortti 65

Kortti 66

Kortti 67

Kortti 68

Kortti 69

Kortti 70

Kortti 71

Kortti 72

Kortti 73

Kortti 74

Kortti 75

Kortti 76

Kortti 77