Staging deployment added for main branch
Merged pull requests now deploy automatically to a staging URL, giving developers a real environment to test changes without waiting for the next CLI release.
Merged changes had nowhere to go until a full CLI release shipped — a bottleneck for catching issues early. A new automated workflow closes that gap by deploying the main branch to a dedicated staging URL whenever changes land. The pipeline runs the in-repo CLI to analyze the codebase, builds the Next.js site, and pushes the result to gitpulse-main.vercel.app using Vercel's production target flag. Developers can now exercise merged work on a real URL immediately after squash merges. Production deployment stays unchanged, still validating against the released CLI to keep the consumer-facing path tested end-to-end.