diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-16 06:07:06 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-10-16 06:07:06 +0000 |
| commit | 3546e1bb0971347e9e9984de0799e3fb53743b33 (patch) | |
| tree | f65e47d5deb95905aa419ebd70ce02c7b32ddb8f /doc/ci/review_apps | |
| parent | f155cc9034f2247c5d368f9b0212ad44248b0c5e (diff) | |
| download | gitlab-ce-3546e1bb0971347e9e9984de0799e3fb53743b33.tar.gz | |
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 7a1e6e4e1b8..da92fadafc4 100644 --- a/doc/ci/review_apps/index.md +++ b/doc/ci/review_apps/index.md @@ -24,8 +24,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. -- Once the review as passed, `topic branch` is merged into `master` where it's deploy to staging. -- After been approved in staging, the changes that were merged into `master` are deployed in to production. +- Once 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. ## How Review Apps work |