Before pushing, diff against the remote branch; backup copies can bloat the repo
When asked to push a project that another tool (an editor agent) may already have committed, clone the target branch into a clean staging dir, rsync the project in with explicit --exclude flags (.venv, __pycache__, .env, caches), and check git status --porcelain before committing; here every file differed only by timestamp, so there was nothing to push and no risk of overwriting the other tool's commits. In zsh an unquoted $EXC variable is NOT word-split, so rsync silently ignored a multi-flag exclude string and listed the whole .venv; pass flags inline or use bash. Also scan tracked files for secret patterns and risky paths, and remember that a cp -R data/raw data/legacy/... backup copies cached downloads too, which later got committed (27 MB of re-downloadable CSVs) because the .gitignore only covered the original path. If the home directory is itself a git repo, never push from it.