Analysis updated 2026-05-18
Deploy a private or enterprise repository to Vercel when native Git integration is not allowed.
Deploy only one package of a monorepo by pointing the action at its working directory.
Skip a Vercel build automatically when a commit does not touch the relevant folder.
Post an updating pull request comment with the live preview link and deployment status.
| spectra010s/d-vercel | 0xradioac7iv/tempfs | 52191314/web-agent-proxy-sdk | |
|---|---|---|---|
| Stars | 0 | 0 | 0 |
| Language | TypeScript | TypeScript | TypeScript |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 3/5 | 4/5 |
| Audience | ops devops | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a Vercel token plus your organization and project IDs stored as GitHub Actions secrets.
d-vercel is a GitHub Action that deploys frontend and full stack applications to Vercel directly from a GitHub Actions workflow. It wraps the Vercel command line tool so it can pull your project configuration, run the deployment, print out the resulting deployment URL, and optionally post an updating status comment on the pull request that triggered it. It is aimed at teams who cannot use Vercel's built in Git integration, for example because of organization security policies on a private or enterprise repository, or because they run a monorepo built with tools like Turborepo, Nx, or pnpm workspaces and need to control exactly which folder gets deployed. It also suits teams who want a custom pipeline, gating deployments behind other checks or running tests such as Cypress or Playwright before or after deploying. The action creates a single sticky comment on a pull request showing the deployment status, preview link, commit hash, and run logs, and updates that same comment on every new commit instead of adding a new one each time. It has native support for working inside a subfolder, which makes monorepo setups straightforward, and it can run a custom check before building so that unrelated changes do not waste build minutes on Vercel. To use it, you first create a Vercel token and find your organization and project IDs in your Vercel account, then store them as GitHub Actions secrets. From there you add a short YAML workflow file that calls the action with those secrets, and it handles pulling configuration and deploying as either a production or preview build. Inputs let you set the working directory, choose whether to fail the workflow on a deployment error, pick a specific Vercel CLI version, and customize the comment title. It outputs the deployment URL and a final status of success, failure, or ignored.
A GitHub Action that deploys apps to Vercel from your own CI pipeline, with monorepo support and auto updating pull request comments.
Mainly TypeScript. The stack also includes TypeScript, GitHub Actions, Vercel CLI.
The README does not state a license, so terms of use and redistribution are unclear.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.