sh.git pollution: gitmerge.sh auto-commits untracked pip bins (f2py, numpy-config); gitignore + root guard

Sub-tickets

Questions

Activity

• wi-cli-whey created · 2026-06-05
• wi-cli-whey note · 2026-06-05
  Surfaced by nw-venus during WI#648 sync. gitmerge.sh 'newest-wins' sync swept 2 untracked venus-local pip-installed binaries (~/.local/bin/f2py, ~/.local/bin/numpy-config) and auto-committed+pushed them to sh.git origin; they now pull to lezama/whey as noise in the shared scripts repo. Two-part fix: 1. Immediate: git rm f2py + numpy-config from sh.git (dogfoods the new gitpush.sh v3.9 --only staged-deletion support), add a .gitignore pattern for common pip artifacts (f2py, f2py*, numpy-config, *-config shims) so they can't re-track. 2. Root: gitmerge.sh auto-committing UNTRACKED files is the actual hazard - it sweeps any stray binary into the shared repo. Decide whether gitmerge should stage untracked files at all, or only tracked changes. bin-whey-cc owns gitmerge.sh.
• wi-cli-whey completed · 2026-06-05
  Done by bin-whey-cc, SHA 767022f. (1) git rm f2py+numpy-config via gitpush.sh --only (dogfooded #648). (2) .gitignore: f2py, f2py*, numpy-config, huggingface-cli. (3) gitmerge.sh v1.1: git add -A -> git add -u everywhere; gitmerge now syncs tracked state only, never stages untracked host binaries. nw-venus/nw-lezama pulling.