From 275430513599cf4c0b8c29fae1776e62793faec5 Mon Sep 17 00:00:00 2001 From: byt3h3ad Date: Sun, 16 Jun 2024 22:11:57 +0530 Subject: [PATCH] new file: deploy-an-app-without-pushing-an-empty-commit.md --- ...-an-app-without-pushing-an-empty-commit.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 vercel/deploy-an-app-without-pushing-an-empty-commit.md diff --git a/vercel/deploy-an-app-without-pushing-an-empty-commit.md b/vercel/deploy-an-app-without-pushing-an-empty-commit.md new file mode 100644 index 0000000..ef5c69f --- /dev/null +++ b/vercel/deploy-an-app-without-pushing-an-empty-commit.md @@ -0,0 +1,26 @@ +# Deploy An App Without Pushing An Empty Commit + +The [Vercel CLI](https://vercel.com/docs/cli) allows you to make updated +deployments of an app right from the command line. + +Many providers require you to push a new commit to the main branch to trigger a +deployment. If there are changes, you can trigger a deployment by pushing +these. If there aren't changes, but you want to re-deploy what is already +there, then you have to create an empty commit and push that. + +With the [Vercel CLI](https://vercel.com/docs/platform/deployments#vercel-cli), +you can re-deploy your app without pushing commits. You do this by including +the `--force` flag. + +To re-deploy the preview environment: + +```bash +$ vercel --force +``` + +To re-deploy the production environment: + +```bash +$ vercel --prod --force +``` +