Git & Version Control · Question Set

Committing, Staging & History — Essentials – Git & Version Control interview questions

Committing, Staging & History — Essentials interview questions for placements and exams.

Subject: Git & Version ControlDifficulty: Mixed14 questions in this set

Set overview

Questions

Included in this set

Subject

Git & Version Control

Explore more sets

Difficulty

Mixed

Level of this set

Git & Version Control – Committing, Staging & History — Essentials questions (14)

Go through each question and its explanation. Use this set as a focused practice pack for Git & Version Control.

Back to Git & Version Control subject page

1. What is `git reflog` and when is it indispensable?

Difficulty: MediumType: SubjectiveTopic: Reflog

Reflog records movements of HEAD and refs (even orphaned). It’s crucial for recovering "lost" commits after resets/rebases or branch deletions.

2. You want to discard local changes in `app.js` and reset it to the last commit. Modern command?

Difficulty: MediumType: MCQTopic: Restore

`git restore <path>` replaces the file from HEAD (modern replacement for `checkout --`).

3. How do you find a commit by message and then show its patch?

Difficulty: MediumType: SubjectiveTopic: Git Log

Use `git log --grep "keyword"` to locate by message; then `git show <hash>` (optionally `-p --stat`) to view the diff and metadata.

4. Which flag creates a GPG-signed commit (assuming GPG is configured)?

Difficulty: MediumType: MCQTopic: Signed Commits

`-S` signs the commit. Configure with `user.signingkey` and GPG agent beforehand.

5. Which command shows a compact, decorated graph of commits for review?

Difficulty: EasyType: MCQTopic: Git Log

This combo visualizes branch tips and relationships succinctly across all refs.

6. How do you stage only parts (hunks) of a file interactively?

Difficulty: MediumType: MCQTopic: Staging

`git add -p` lets you review and stage hunks interactively for granular commits.

7. Describe two best practices for writing commit messages.

Difficulty: EasyType: SubjectiveTopic: Commit Hygiene

Keep subject line ≤50 chars in imperative mood (e.g., "Fix crash on null input"). Add a blank line, then a body explaining what and why (context, impact, links).

8. You forgot to include one file in the last commit. Which sequence is correct?

Difficulty: EasyType: MCQTopic: Commit Amend

Stage the missing change, then amend to rewrite the tip commit (avoid on public history).

9. Which command unstages a file but keeps its working tree changes?

Difficulty: EasyType: MCQTopic: Staging

`restore --staged` removes from Index only; the file contents remain in the working tree.

10. Compare `git reset --soft`, `--mixed` (default), and `--hard`.

Difficulty: MediumType: SubjectiveTopic: Reset

`--soft` moves HEAD only (keeps Index/WT), `--mixed` moves HEAD and resets Index (keeps WT), `--hard` resets HEAD, Index, and Working Tree (destructive).

11. Which command compares staged changes to the last commit?

Difficulty: MediumType: MCQTopic: Status Diff

`--staged` (aka `--cached`) shows Index vs HEAD; plain `git diff` shows WT vs Index.

12. Explain `git commit --fixup` and `git rebase --autosquash` workflow.

Difficulty: MediumType: SubjectiveTopic: Autosquash

`--fixup <hash>` creates a targeted fix commit labeled for autosquash. Later `rebase -i --autosquash` reorders and squashes fixups onto their intended commits automatically, keeping a tidy history.

13. Which command stages all modified and deleted files but not untracked files?

Difficulty: EasyType: MCQTopic: Staging

`-u` stages tracked file modifications and deletions; it skips new untracked files.

14. What is the Git Index (staging area) and why does Git use it?

Difficulty: EasyType: SubjectiveTopic: Staging

The Index is a middle layer between your working tree and the repository. You choose exactly which changes to include in the next snapshot (commit), enabling partial commits and clean, reviewable history.

More sets in Git & Version Control

Git & Version Control — Fundamentals(14+ Questions)
Git Branching & Collaboration — Core(14+ Questions)
Remotes, Sync & Tags — Collaboration Deep Dive(14+ Questions)
Branching Strategies & Merge vs Rebase — History Hygiene(14+ Questions)
Rewriting History Safely — Reset, Revert, Reflog, Restore(14+ Questions)
Branching & Merging Strategies — Merge, Rebase, Fast-Forward(14+ Questions)
Stashing, Cleaning & Working Tree Maintenance(13+ Questions)
Branching Strategies, Pull Requests & Collaboration(13+ Questions)
Rebase, Cherry-pick & History Rewriting (Advanced)(12+ Questions)
Tags, Releases & Versioning (SemVer) in Git(13+ Questions)
Collaboration Workflows, Code Review & Best Practices(14+ Questions)

Explore related subjects

HTML CSS Javascript Typescript SQL & Databases React

Continue your preparation

For complete preparation, combine this set with full subject-wise practice for Git & Version Control. You can also explore other subjects and sets from the links below.

Quick navigation:Git & Version Control subject page•All subjects

Subject page

Git & Version Control · Question Set

Committing, Staging & History — Essentials – Git & Version Control interview questions

Committing, Staging & History — Essentials interview questions for placements and exams.

Subject: Git & Version ControlDifficulty: Mixed14 questions in this set

Set overview

Questions

Included in this set

Subject

Git & Version Control

Explore more sets

Difficulty

Mixed

Level of this set

Git & Version Control – Committing, Staging & History — Essentials questions (14)

Go through each question and its explanation. Use this set as a focused practice pack for Git & Version Control.

Back to Git & Version Control subject page

1. What is `git reflog` and when is it indispensable?

Difficulty: MediumType: SubjectiveTopic: Reflog

Reflog records movements of HEAD and refs (even orphaned). It’s crucial for recovering "lost" commits after resets/rebases or branch deletions.

2. You want to discard local changes in `app.js` and reset it to the last commit. Modern command?

Difficulty: MediumType: MCQTopic: Restore

`git restore <path>` replaces the file from HEAD (modern replacement for `checkout --`).

3. How do you find a commit by message and then show its patch?

Difficulty: MediumType: SubjectiveTopic: Git Log

Use `git log --grep "keyword"` to locate by message; then `git show <hash>` (optionally `-p --stat`) to view the diff and metadata.

4. Which flag creates a GPG-signed commit (assuming GPG is configured)?

Difficulty: MediumType: MCQTopic: Signed Commits

`-S` signs the commit. Configure with `user.signingkey` and GPG agent beforehand.

5. Which command shows a compact, decorated graph of commits for review?

Difficulty: EasyType: MCQTopic: Git Log

This combo visualizes branch tips and relationships succinctly across all refs.

6. How do you stage only parts (hunks) of a file interactively?

Difficulty: MediumType: MCQTopic: Staging

`git add -p` lets you review and stage hunks interactively for granular commits.

7. Describe two best practices for writing commit messages.

Difficulty: EasyType: SubjectiveTopic: Commit Hygiene

Keep subject line ≤50 chars in imperative mood (e.g., "Fix crash on null input"). Add a blank line, then a body explaining what and why (context, impact, links).

8. You forgot to include one file in the last commit. Which sequence is correct?

Difficulty: EasyType: MCQTopic: Commit Amend

Stage the missing change, then amend to rewrite the tip commit (avoid on public history).

9. Which command unstages a file but keeps its working tree changes?

Difficulty: EasyType: MCQTopic: Staging

`restore --staged` removes from Index only; the file contents remain in the working tree.

10. Compare `git reset --soft`, `--mixed` (default), and `--hard`.

Difficulty: MediumType: SubjectiveTopic: Reset

`--soft` moves HEAD only (keeps Index/WT), `--mixed` moves HEAD and resets Index (keeps WT), `--hard` resets HEAD, Index, and Working Tree (destructive).

11. Which command compares staged changes to the last commit?

Difficulty: MediumType: MCQTopic: Status Diff

`--staged` (aka `--cached`) shows Index vs HEAD; plain `git diff` shows WT vs Index.

12. Explain `git commit --fixup` and `git rebase --autosquash` workflow.

Difficulty: MediumType: SubjectiveTopic: Autosquash

`--fixup <hash>` creates a targeted fix commit labeled for autosquash. Later `rebase -i --autosquash` reorders and squashes fixups onto their intended commits automatically, keeping a tidy history.

13. Which command stages all modified and deleted files but not untracked files?

Difficulty: EasyType: MCQTopic: Staging

`-u` stages tracked file modifications and deletions; it skips new untracked files.

14. What is the Git Index (staging area) and why does Git use it?

Difficulty: EasyType: SubjectiveTopic: Staging

More sets in Git & Version Control

Git & Version Control — Fundamentals(14+ Questions)
Git Branching & Collaboration — Core(14+ Questions)
Remotes, Sync & Tags — Collaboration Deep Dive(14+ Questions)
Branching Strategies & Merge vs Rebase — History Hygiene(14+ Questions)
Rewriting History Safely — Reset, Revert, Reflog, Restore(14+ Questions)
Branching & Merging Strategies — Merge, Rebase, Fast-Forward(14+ Questions)
Stashing, Cleaning & Working Tree Maintenance(13+ Questions)
Branching Strategies, Pull Requests & Collaboration(13+ Questions)
Rebase, Cherry-pick & History Rewriting (Advanced)(12+ Questions)
Tags, Releases & Versioning (SemVer) in Git(13+ Questions)
Collaboration Workflows, Code Review & Best Practices(14+ Questions)

Explore related subjects

HTML CSS Javascript Typescript SQL & Databases React

Continue your preparation

For complete preparation, combine this set with full subject-wise practice for Git & Version Control. You can also explore other subjects and sets from the links below.

Quick navigation:Git & Version Control subject page•All subjects

Committing, Staging & History — Essentials – Git & Version Control interview questions

Set overview

1. What is `git reflog` and when is it indispensable?

2. You want to discard local changes in `app.js` and reset it to the last commit. Modern command?

3. How do you find a commit by message and then show its patch?

4. Which flag creates a GPG-signed commit (assuming GPG is configured)?

5. Which command shows a compact, decorated graph of commits for review?

6. How do you stage only parts (hunks) of a file interactively?

7. Describe two best practices for writing commit messages.

8. You forgot to include one file in the last commit. Which sequence is correct?

9. Which command unstages a file but keeps its working tree changes?

10. Compare `git reset --soft`, `--mixed` (default), and `--hard`.

11. Which command compares staged changes to the last commit?

12. Explain `git commit --fixup` and `git rebase --autosquash` workflow.

13. Which command stages all modified and deleted files but not untracked files?

14. What is the Git Index (staging area) and why does Git use it?

More sets in Git & Version Control

Explore related subjects

Continue your preparation

Master Interviews Anywhere, Anytime

Committing, Staging & History — Essentials – Git & Version Control interview questions

Set overview

1. What is `git reflog` and when is it indispensable?

2. You want to discard local changes in `app.js` and reset it to the last commit. Modern command?

3. How do you find a commit by message and then show its patch?

4. Which flag creates a GPG-signed commit (assuming GPG is configured)?

5. Which command shows a compact, decorated graph of commits for review?

6. How do you stage only parts (hunks) of a file interactively?

7. Describe two best practices for writing commit messages.

8. You forgot to include one file in the last commit. Which sequence is correct?

9. Which command unstages a file but keeps its working tree changes?

10. Compare `git reset --soft`, `--mixed` (default), and `--hard`.

11. Which command compares staged changes to the last commit?

12. Explain `git commit --fixup` and `git rebase --autosquash` workflow.

13. Which command stages all modified and deleted files but not untracked files?

14. What is the Git Index (staging area) and why does Git use it?

More sets in Git & Version Control

Explore related subjects

Continue your preparation

Master Interviews
Anywhere, Anytime