Site URL auto-detected from Vercel, Netlify, Cloudflare Pages
Deploying gitpulse no longer requires setting GITPULSE_SITE_URL manually — the CLI now detects your site URL automatically from Vercel, Netlify, and Cloudflare Pages environment variables at build time.
When deploying to hosted platforms, manually configuring the site URL was a recurring friction point. Every fresh deploy meant updating an environment variable, and preview deployments had no straightforward way to point the analyzer at the right URL.
Gitpulse now reads the site URL directly from the platform. When running on Vercel, Netlify, or Cloudflare Pages, the CLI checks the platform's native environment variables — VERCEL_PROJECT_PRODUCTION_URL, VERCEL_URL, URL, DEPLOY_PRIME_URL, DEPLOY_URL, or CF_PAGES_URL — and uses whichever is set. An explicit GITPULSE_SITE_URL still overrides when needed, such as with custom domains.
The CLI is also now properly packaged with its README and LICENSE included in the npm tarball — version 0.1.2 shipped without them because the files array referenced paths that didn't exist in the cli/ directory. A prepack script copies them from the repo root before packing.
For Vercel deployments, a new GitHub Actions workflow uses the published CLI in CI to run analyze and build, then ships the prebuilt output to Vercel via vercel deploy --prebuilt. Vercel runs no build and sees no API keys.