padosoft-git-commit-integritylisted

# Git commit integrity **What git recorded is not always what you changed.** Two failures produce that gap, both invisible on the machine that made the commit, both cheap to check and expensive to find later: 1. files you believe you committed and that are **not there**; 2. files that are there but **differ** from what you wrote. --- ## 1. After every commit: look at what went in ```bash git show --stat HEAD ``` Compare the file count against the list of what you meant to change — new plus modified. **If the count does not add up, investigate before pushing.** This takes two seconds and is the only moment at which the next failure is cheap. ## 2. Files missing from the commit **`git add -A` skips the files excluded by `.gitignore` in silence.** No error, no warning, exit code 0. The shape to recognise: a generic `logs/` pattern, written for runtime logs, swallows a **source** directory that happens to be called `logs/`. Build, server and tests stay green locally — the files are simply absent from the commit, so the feature does not exist for anyone else. ```bash git status --short # what is still outside, compared with what you expected git check-ignore -v path/to/file # prints the .gitignore line responsible ``` The fix is a **negation in `.gitignore`**, next to the rule that caused it: ```gitignore logs/ !**/otel/logs/ # sources, not runtime logs ``` ⚠️ **Not `git add -f`.** It puts this one file in and leaves the trap armed for every futu