diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-03-02 00:11:09 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-03-02 00:11:09 +0300 |
| commit | 11b7785066d3e81916cbf653f4eb6568148f7e01 (patch) | |
| tree | d4e66091e1cbef57db10d2c9c16cd98106e9a633 /doc/ci/review_apps | |
| parent | 69f0d90aad454a2b8f3c4e2f2ca31886a14a8642 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/review_apps')
| -rw-r--r-- | doc/ci/review_apps/index.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/review_apps/index.md b/doc/ci/review_apps/index.md index b44526135a1..fc83c45763a 100644 --- a/doc/ci/review_apps/index.md +++ b/doc/ci/review_apps/index.md @@ -31,8 +31,8 @@ In the above example: - A Review App is built every time a commit is pushed to `topic branch`. - The reviewer fails two reviews before passing the third review. -- After the review has passed, `topic branch` is merged into `master` where it is deployed to staging. -- After having been approved in staging, the changes that were merged into `master` are deployed in to production. +- After the review passes, `topic branch` is merged into the default branch, where it's deployed to staging. +- After its approval in staging, the changes that were merged into the default branch are deployed to production. ## How Review Apps work |