Skip to content

docs: document redeploying recent deployments #5029

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
mintlify wants to merge 1 commit into
base: main
Choose a base branch
from
+18 −0
Draft

docs: document redeploying recent deployments #5029

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/deployment/atomic-deployment.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,6 +147,8 @@ Three ways out, in order of preference:
- **Pass `--force`**, if you drive deploys yourself.
- **Use an id that captures more than the commit** — `${GITHUB_SHA}-${GITHUB_RUN_ID}`, say — if your builds legitimately depend on inputs outside the tree. You lose idempotency in exchange.

For a deployment from the GitHub integration in the last 7 days, you can also [redeploy it from the dashboard](/deployment/overview#redeploying-from-the-dashboard). This builds the same commit again even though a deployment with that id already exists.

See the [deploy command reference](/cli-deploy-commands) for all deploy flags.

## Automatic discovery
Expand Down
16 changes: 16 additions & 0 deletions docs/deployment/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,6 +160,22 @@ Or from the dashboard:

To keep your app and tasks in sync without coordinating promotion at all, see [atomic deployments](/deployment/atomic-deployment).

### Redeploying from the dashboard

You can rebuild a recent deployment as a new deployment from the **Deployments** page. Open the menu on the deployment's row and select **Redeploy**.

The **Redeploy** action is available for deployments that:

- Have finished: deployed, failed, canceled or timed out.
- Were created in the last 7 days.
- Were triggered by the [GitHub integration](/github-integration), or deployed from the CLI with `--native-build` and without `--local-bundle`.

A GitHub integration deployment is rebuilt from the same commit and branch. A CLI deployment is rebuilt from the source files uploaded for the original deployment.

The new deployment gets a new version. **Promote deployment automatically** is selected by default, so the new version becomes the current version once it deploys successfully. Clear the checkbox to [skip promotion](#skipping-promotion) and promote it later. The new deployment's page shows the deployment it was redeployed from under **Redeploy of**.

You can't redeploy while another deployment is in progress in the same environment. If your production environment uses [atomic deployments with Vercel](/vercel-integration#atomic-deployments), redeploy it from Vercel instead.

## Staging deploys

By default, the `deploy` command will deploy to the `prod` environment. If you want to deploy to a different environment, you can use the `--env` flag:
Expand Down
Loading