Audit package sync status across monorepo subtrees
Session from 0xKobolds on Hugging Face by moikapy · MIT · condensed by Coders Talk
Click a segment to jump to that moment
2msession
0interventions
by library · 23h
GOAL
Check which packages in a monorepo are synced with their GitHub remotes and get details on what's drifted.
- +0Prompt · +0pkg
- +0mAgent did · +0mRan package sync status check across org, found 3 synced, 9 drifted, 8 with no repo
- +0mPrompt · +0mlist
- +1mAgent did · +1mTried git diff and git subtree diff against local HEAD across the 9 drifted packages, but these returned empty results
- +1mAgent did · +1mSwitched to diffing against the actual remote subtree branches, revealing real drift: pi-kobold +12,278 lines, pi-learn +13,112, pi-gateway +4,630, plus smaller drifts in pi-wallet, pi-secret-guardian, pi-erc8004; three packages showed no remote diff
- +2mOutcome · +2mProduced a drift report table by package (files, insertions, key additions) showing all unpushed changes are ahead of the GitHub remotes; no push performed yet
VERDICT
Next time I'd ask directly for the subtree-vs-remote diff instead of starting with plain git diff, since that returned nothing useful for several rounds. The fix that actually worked was comparing against the remote subtree branches rather than local HEAD, which is what finally surfaced the real drift numbers.