diff options
| author | Grzegorz Bizon <grzesiek.bizon@gmail.com> | 2016-11-21 11:27:28 +0100 |
|---|---|---|
| committer | Grzegorz Bizon <grzesiek.bizon@gmail.com> | 2016-11-21 11:27:28 +0100 |
| commit | c6a4f9fc5b98024d4af872b0009b90c36bc2e595 (patch) | |
| tree | c945102da813fb098bdbdaeb65bd6fc5cb69b72e /doc/development | |
| parent | d07ef089c8870b4a5a1c69555c54c93ff1f1fa24 (diff) | |
| download | gitlab-ce-c6a4f9fc5b98024d4af872b0009b90c36bc2e595.tar.gz | |
Update some docs to reflect MWPS name change
Diffstat (limited to 'doc/development')
| -rw-r--r-- | doc/development/code_review.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/code_review.md b/doc/development/code_review.md index c5c23b5c0b8..4bf0e7197e9 100644 --- a/doc/development/code_review.md +++ b/doc/development/code_review.md @@ -70,8 +70,8 @@ experience, refactors the existing code). Then: - After a round of line notes, it can be helpful to post a summary note such as "LGTM :thumbsup:", or "Just a couple things to address." - Avoid accepting a merge request before the build succeeds. Of course, "Merge - When Build Succeeds" (MWBS) is fine. -- If you set the MR to "Merge When Build Succeeds", you should take over + When Pipeline Succeeds" (MWPS) is fine. +- If you set the MR to "Merge When Pipeline Succeeds", you should take over subsequent revisions for anything that would be spotted after that. ## Credits |