What is .gitignore and why does it matter in a MERN repo?
PICTURE THIS: STACK VS QUEUE
Simple meaning
.gitignore lists paths Git should not track, such as node_modules, build output, and .env files.
WHY — Git instead of guessing?
Why interviewers care about Git:
who only read docs from people who shipped.
and tied to Full Stack work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1.gitignore lists paths Git
should not track, such as node_modules, build output, and .env files.
- 2Ignoring generated and secret
files keeps the repo small and safer.
- 3If a file was
already committed, adding it to .gitignore is not enough
- 4you must untrack it
as well.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
.gitignore lists paths Git should not track, such as node_modules, build output, and .env files. Ignoring generated and secret files keeps the repo small and safer.