← Commit history

Record the commit:null gitignore trap for binary/hero pushes (server honors repo .gitignore; unignore + verify md5)

John Lauer ·9c02218805 · ·parent b5f9e68
1 file changed +8
skills/pup-bridge-publish/SKILL.md+8
@@ -217,3 +217,11 @@ bespoke `start_browser_bridge` npm-installs only the BUNDLED copy; the cache cop After any release/repo-push/pkg-publish, refresh the LIVE wiki page in a pup window the user can see (`browser_navigate` the existing session to `https://wiki.adom.inc/adom/adom-desktop-puppeteer-bridge?v=<ver>`, cache-busted), screenshot it, and hand over the link. Never report "published" without showing it.++## Binary/hero pushes: `ok:true, commit:null` = the server honored the repo .gitignore++`repo push` (and the raw files API) return `{ok:true, files_count:1}` but `commit:null` and the file+NEVER lands when the repo's committed `.gitignore` matches it (this repo ignores `*.png`). No error is+raised — the only tell is `commit:null` + a 404 on the file. Fix: add a `!hero-vN.png` unignore line,+push `.gitignore` FIRST (real commit hash returned), then push the PNG, then verify anonymously:+HTTP 200 AND `md5sum` matches the local file. Use a NEW versioned filename per hero (CDN staleness).