Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Commands**: git restore <file> (unstaged); git restore --staged <file> (staged); git reset --hard HEAD (all). git stash for reversible save. **Why Care**: --hard is destructive; in CI/CD use git clean -fd for untracked. Never --hard on shared branches without alignment....
Commands: git restore <file> (unstaged); git restore --staged <file> (staged); git reset --hard HEAD (all). git stash for reversible save.
Why Care: --hard is destructive; in CI/CD use git clean -fd for untracked. Never --hard on shared branches without alignment.
Pro-Move: Always git status; git diff before discarding. Safer: stash first.
Red Flag: Using --hard casually. Pro-Move: 'I prefer stash when unsure—recoverable.'
According to DataEngPrep.tech, this is one of the most frequently asked General/Other interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.