Sometimes I solve the same problem twice. A bug eats an afternoon, I find the fix, and a few weeks later I hit a similar problem and forgot how to solve it. So I’m starting a log: an honest record of the work behind GitProxy to help myself and future users, as well as the general public solve the same problems, much, much faster.
About GitProxy
GitProxy sits between developers and a Git remote endpoint such as github.com, and ensures that all outgoing git push operations are compliant with organizational policy. It aims to enable developers to contribute to open source, while addressing the myriad of legal and compliance requirements that firms have in place. It’s a FINOS project, MIT-licensed, and contributions are welcome. Installation and configuration are covered in the git-proxy documentation, and the package itself is published as @finos/git-proxy on npm.
npx -y @finos/git-proxyWhat ends up in the log
Most entries are one specific problem and the fix, written so you can apply it to your own variant rather than only the exact case in front of me. A few that show the usual shape: a Vitest mock that silently did nothing because vi.mock is hoisted, a container that died on startup with EACCES: permission denied, mkdir, a dev server that would not start because of an inotify limit reported as ENOSPC, and an npm publish that could not authenticate after moving to trusted publishers.
Longer pieces show up when the work earns it, like moving a whole test suite from Mocha and Chai to Vitest or putting an LLM behind GitHub Actions to triage incoming issues. To browse by subject instead, the topics page lists everything by tag.
How often to expect updates
I hope to share progress at least once a week. Feel free to subscribe via RSS if you want updates as they land. If any of this saves you an hour or two, star the repo!