Q: What is a `.gitkeep` file, and why do you sometimes see empty files with that name committed to repos?
Git does not track empty directories. If you create logs/ with nothing in it and run git add logs/, nothing happens — Git has nothing to track because the directory has no files.
Want to master this scenario in a live sandbox? KodeKloud's Advanced Git Workflows, Rebase & Interactive Diagnostics covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Git is an immutable directed acyclic graph (DAG); knowing commands like git reflog means you never truly lose commits. The interviewer is testing: Understanding that Git tracks content, not directories.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Git does not track empty directories. If you create logs/ with nothing in it and run git add logs/, nothing happens — Git has nothing to track because the directory has no files.
- Ensuring a
tmp/,logs/, oruploads/directory exists when someone clones the repo (the app expects the directory to exist at runtime). - Skeleton project templates where the directory structure matters.
Remediation & Permanent Safeguards
.gitkeep is a convention (not a Git feature) — it's an empty file placed inside an otherwise-empty directory so Git will track the directory. The name .gitkeep is arbitrary; you could use .placeholder or any filename. .gitkeep is just the community convention. Common use cases: If the directory should exist but its *contents* should be ignored (e.g., logs/ should be present but log files shouldn't be committed), combine both: This ignores everything inside logs/ except the .gitkeep file, preserving the directory.
# .gitignore
logs/*
!logs/.gitkeep
- Ensuring a tmp/, logs/, or uploads/ directory exists when someone clones the repo (the app expect...
- Skeleton project templates where the directory structure matters.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
-
Running raw git push --force rather than git push --force-with-lease on shared team feature branches when configuring gitkeep file sometimes
git push --forceunconditionally overwrites remote commits made by teammates, whereas--force-with-leaseaborts if the remote ref was updated. - Resolving complex merge conflicts with blind checkout overwrite strategies without running unit tests when configuring gitkeep file sometimes Unilateral conflict resolution frequently clobbers complementary logic introduced in parallel feature branches, creating regression bugs.
-
Discarding corrupted working directories prematurely instead of recovering lost state using git reflog when configuring gitkeep file sometimes
git reflogtracks every HEAD movement, allowing instant recovery of discarded commits, botched rebases, or deleted local branches. - Disabling branch protection rules and mandatory PR approval reviews on shared release branches when configuring gitkeep file sometimes Without branch protection, developers can bypass CI validation gates and push untested code directly to production branches.