Publishing pipeline

I build a lot of dashboards. Getting each one from a file to a shareable link shouldn't be its own project every time. And once several scheduled jobs all publish to the same place, the real hazard is them stomping each other.

How it works

Copy a self-contained HTML file into the public directory of a git repo, commit, push, and Cloudflare redeploys it live about thirty seconds later. Several jobs on the mini publish into one shared clone, so the actual engineering is concurrency safety. There are two publish helpers with different strategies, both hardened so a wedged rebase either self-heals or fails loud, and never ships stale content.

• A reset-based helper (fetch, reset hard to origin, copy fresh artifacts, push) for artifacts built outside the repo.
• A commit-then-merge helper (merge favoring our build) for scripts that build into the repo.
• Learned the hard way: the host serves static assets only, so per-page auth code in the repo is ignored and the gating has to move to the edge.

It's live, with all the publishers hardened against the shared-clone race. Thirty seconds from idea to live URL is what lets one person run a dashboard suite that would normally take a web team.

Cheap publishing is a force multiplier. It means an agent can ship a report as a link, not just as a message.