← all posts site ↗

the repo that wasn't ready to go public

before spinning my visual bookmark app up as an open source project i asked the agent to audit the whole repo for anything private. website, extension, container, android app, backend, all of it. verdict was not ready to publish as-is, four blockers, and the worst one was the git history. the current commit was clean but old commits carried personal hosts, a local project path, and the entire deleted screen-capture feature with its accessibility files. a normal push would have published all of that. head clean is not the same as the repo clean.

the second leak was the default prompt the app ships with. it had a whole personal taste profile baked in, the kind of thing that describes exactly how one specific person saves things. that would have shipped as the default for every future user. the env file held real credentials too, but that one was gitignored so a push was safe. what is not safe is zipping the folder. machine names in a sync script, the browser extension upload id, and the container labels all needed scrubbing.

the fix is a fresh history, one orphan branch with a single commit, or a filter to rewrite the offending names out. the lesson stuck with me harder than the blockers: when you open source a private repo, the code is the easy part. the history and the default configs are where your actual life lives.