Images are reused AI-generated editorial illustrations, not documentary photographs or verified product screenshots.
The meaning of git add dot is simple but easy to misuse: git add . stages eligible changes under the current directory. It prepares content for a commit; it does not create the commit or publish anything. In a client repository, the important question is which files and changes the current directory includes.
Inspect the working tree and directory
Run git status and confirm where you are. The dot is a pathspec for the current directory, so running the command from a subdirectory differs from running it at the repository root. Review ignored files and generated outputs under the project’s rules; ignore settings do not make tracked sensitive files safe.
Prefer a deliberate staging boundary
Use specific paths when you know exactly what belongs in the change. git add -p can stage selected hunks when appropriate. Modern git add can also stage removals under the chosen pathspec. Do not treat the command as a harmless save button, especially after downloading credentials, exporting customer data or generating large artifacts.
Review the staged snapshot before committing
Run git diff --cached and inspect git status after staging. Subsequent edits may remain unstaged, so the working file and staged version can differ. If a secret is already committed or exposed, merely removing it from a later commit is not enough; follow the client’s credential rotation and incident procedure.
A practical checklist
- Check the current directory and repository.
- Review changed and untracked files.
- Stage specific paths or hunks where practical.
- Inspect the staged diff for secrets and unrelated edits.
- Commit only after the staged snapshot passes review.
Worked example
Illustrative example: a freelancer edits a page template and also creates a local test export. Before staging, status reveals both files. They stage only the template, inspect the staged diff and keep the export outside version control. A broad add command without review would have mixed unrelated material into the deliverable.
Common questions
Does add upload a file? No. Does . include the whole repository from any directory? No; its scope depends on the current directory. Can files change after staging? Yes, so review staged and unstaged differences separately.
What to do next
Make staged-diff review a habit before every client commit. It is a practical quality and confidentiality check, not an optional cleanup after publication.