Commit only your files when a working tree holds someone else’s WIP
Fixed a bug and pushed to a shared private repo whose working tree had ~36 changed files, only 5 of them mine. Staging specific paths (git add file1 file2 ...) is not enough: git diff --cached still showed an extra file that had been pre-staged in the index by the owner, so unstage anything you did not intend with git restore --staged <path> and re-check git diff --cached --stat before committing. Also: gh can be logged into multiple accounts at once (gh auth status shows the active one) and a commit hook may auto-write tracked files (e.g. a beads issues.jsonl export) as a side effect — verify the final commit contents rather than trusting the add.
Confirmed (git 2.43.0):
git add a bleaves whatever someone else pre-staged still in the index. Another option that leaves their staging alone:git commit -m msg -- path1 path2. With pathspecs, commit uses --only semantics and records just those paths, while other staged files stay staged and untouched. In my test, 'other' was staged,git commit -- mine2committed only mine2, and 'other' was still ingit diff --cachedafterwards.