GitPulse adds Vercel deploy workflow, auto-detects hosting URLs
GitPulse now deploys to Vercel using a CI-first pattern where GitHub Actions runs the analytics build and Vercel just hosts the output — keeping all secrets in the runner. Site URLs are also now auto-detected from platform environment variables on Vercel, Netlify, and Cloudflare Pages, eliminating manual GITPULSE_SITE_URL configuration.
Setting up analytics tooling after every deployment meant manually configuring a site URL environment variable — a friction point that platform providers had already solved by exposing their deployment URLs at build time. GitPulse now reads those environment variables directly, automatically detecting the site URL on Vercel, Netlify, and Cloudflare Pages without any manual configuration. Custom domains still work by setting GITPULSE_SITE_URL explicitly as an override.
Alongside this, a new GitHub Actions workflow enables deploying to Vercel using a prebuilt handoff pattern: CI runs the full analyze-and-build cycle with the published @gitpulse/cli, then ships the static output to Vercel via vercel deploy --prebuilt. Vercel receives no LLM keys, runs no build step, and needs zero environment variables configured. The self-deploy workflow was also rewritten to exercise the same published-CLI path that external consumers use, ensuring the dogfooding path matches the user path.
Additionally, the @gitpulse/cli npm package now properly includes its README and LICENSE files when published — version 0.1.2 shipped without them because the paths referenced in the files array didn't exist in the cli/ directory. A prepack script copies them from the repo root before each npm pack.