skills.rest
lurodrisilva
lurodrisilvaCOMMUNITY
Explore all skills by this author →
GitHub

vercel-git-cicd

Configure and debug Git-driven preview and production deployment pipelines on Vercel.

Updated Apr 11, 2026
Search Tags:#Vercel#github actions#monorepo#git integration#ci-cd#preview deployments#deploy hooks
One-click install
npx skills add https://github.com/lurodrisilva/personal-skills --skill vercel-git-cicd-lurodrisilva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vercel-git-cicd
Source: https://github.com/lurodrisilva/personal-skills/tree/main/platform-engineering/vercel-git-cicd
Command: npx skills add https://github.com/lurodrisilva/personal-skills --skill vercel-git-cicd-lurodrisilva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Connecting a Git repository to Vercel looks simple until commits stop triggering deployments, fork PRs hang waiting for authorization, the Ignored Build Step skips everything (or nothing), or a self-hosted Git host cannot be reached by the built-in integration. This Skill provides an operator's playbook for the entire Git-to-Vercel seam, grounded in the official vercel.com/docs/git documentation. ## Core Features & Use Cases - Provider connection and permission triage: Covers GitHub, GitLab, Bitbucket, and Azure DevOps integrations, including permission matrices for "missing Git repository" errors, commit-author membership rules, fork-PR authorization, and verified-commit enforcement. - Branch flow and PR feedback control: Explains production branch resolution, preview/staging branch patterns, git.deploymentEnabled minimatch rules, bot comment silencing, consolidated commit statuses, and triggering CI from repository_dispatch events instead of noisy deployment_status webhooks. - Build gating and external CI bridges: Details the inverted Ignored Build Step contract (exit 0 = skip, exit 1 = build), turbo-ignore, deploy hooks, the VERCEL_GIT_* environment variable surface, and the vercel pull → build → deploy --prebuilt pipeline for GHES, Self-Managed GitLab, Bitbucket Data Center, and Azure DevOps. - Use Case: A team's commits suddenly stop deploying. You use the read-only connection-audit script to confirm the repo wiring, then walk the who-may-deploy rules to discover the commit author is not a member of the Vercel team. ## Quick Start Ask the agent to audit why commits to your repository are not triggering Vercel deployments and to check the project's Git connection, production branch, and fork protection settings.

Frequently Asked Questions about vercel-git-cicd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why are my commits not triggering Vercel deployments?▼

Commits not triggering deployments usually trace to commit-author membership rules, fork protection awaiting authorization, unverified commits being auto-canceled, or a `git.deploymentEnabled` pattern excluding the branch. Check the who-may-deploy rules first before debugging the webhook.

How does the Vercel Ignored Build Step exit code work?▼

The Ignored Build Step contract is inverted: exit code 0 skips the build (deployment shows as ignored) and exit code 1 proceeds with the build. Common commands are `git diff HEAD^ HEAD --quiet -- <path>` or `npx turbo-ignore` for monorepos.

Can I use Vercel with GitHub Enterprise Server or self-hosted GitLab?▼

Self-hosted Git hosts cannot use the built-in integration. Instead, run the CLI bridge in your CI pipeline: `vercel pull --environment=...`, `vercel build`, then `vercel deploy --prebuilt`, on a project with no Git integration attached.

How do I trigger CI after a Vercel preview deployment?▼

Use GitHub `repository_dispatch` events such as `vercel.deployment.success`, which carry the deployment URL in `client_payload.url`. Avoid `deployment_status` webhooks, which are noisy and lack context; the workflow file must exist on the default branch.

What are the limits and risks of Vercel deploy hooks?▼

Deploy hooks accept unauthenticated GET or POST requests, so the URL itself is a credential and must be stored like a token. Limits are 5 hooks per project on Hobby and Pro (10 on Enterprise) and 60 triggers per hour per project.

How does Vercel decide which branch is the production branch?▼

Production branch resolution follows a fixed order: `main`, then `master`, then on Bitbucket the repo's production-branch setting, then the repo default branch. Change it under Project Settings, Environments, Production, Branch Tracking rather than renaming branches.

Related Skills

Explore More Software Engineering Skills→
jvdominojvdomino

domino-projects

Create and configure Domino Projects with integrated Git workflows.

Community
Intermediate
DucCuong159DucCuong159

vercel-deployment

Configure and deploy Next.js applications to Vercel with edge and serverless runtimes.

Community
Intermediate
hicucuhicucu

preventing-github-actions-loops

Detect cyclic trigger paths in GitHub Actions workflow files.

Community
Intermediate
iblaiiblai
15

iblai-ops-deploy

Automate ibl.ai frontend deployments to Vercel and other hosting platforms.

Official
Advanced