From cab15e4dc1d7d34d52d3a00766398dd4979c53b6 Mon Sep 17 00:00:00 2001 From: Shu Uesugi Date: Tue, 11 Feb 2020 14:46:55 -0800 Subject: [PATCH] Update docs/deployment.md Co-Authored-By: Leo Lamprecht --- docs/deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/deployment.md b/docs/deployment.md index 3b852e3f682e574..92e18a773f09c7f 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -28,7 +28,7 @@ Congratulations! You’ve just deployed your Next.js app! If you have questions, Let’s talk about the workflow we recommend using. [ZEIT Now](https://zeit.co) supports what we call the **DPS** workflow: **D**evelop, **P**review, and **S**hip: - **Develop:** When you work on something new, create a new Git branch. -- **Preview:** Every time you push changes to GitHub / GitLab / BitBucket, ZEIT Now automatically creates a new deployment with a unique URL. You can view them on GitHub when you open a pull request or under “Preview Deployments” on your project page on ZEIT Now. [Learn more about it here](https://zeit.co/features/deployment-previews). +- **Preview:** Every time you push changes to GitHub / GitLab / BitBucket, ZEIT Now automatically creates a new deployment with a unique URL. You can view them on GitHub when you open a pull request, or under “Preview Deployments” on your project page on ZEIT Now. [Learn more about it here](https://zeit.co/features/deployment-previews). - **Ship:** When you’re ready to ship, merge the pull request to your default branch (e.g. `master`). ZEIT Now will automatically create a production deployment. By using the DPS workflow, instead of doing _code reviews_, you can do _deployment previews_. Each deployment creates a unique URL that can be shared or used for integration tests.