diff options
| author | Marin Jankovski <maxlazio@gmail.com> | 2017-08-01 13:23:43 +0200 |
|---|---|---|
| committer | Marin Jankovski <maxlazio@gmail.com> | 2017-08-01 13:23:43 +0200 |
| commit | d045709a7b7d9d06712eaea81f53a8e032e0a057 (patch) | |
| tree | f62481999b7fbd6a70fefb5c35b67f178f4353d7 | |
| parent | 03fb9c7ce5747c6546ae9ae108402b49e70e5b82 (diff) | |
| download | gitlab-ce-doc_code_review.tar.gz | |
Remove extra whitespace and add article the.doc_code_review
| -rw-r--r-- | doc/development/code_review.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/code_review.md b/doc/development/code_review.md index 1d69da0912e..64a89976300 100644 --- a/doc/development/code_review.md +++ b/doc/development/code_review.md @@ -12,7 +12,7 @@ There are a few rules to get your merge request accepted: 1. If your merge request includes frontend and backend changes [^1], it must be **approved by a [frontend and a backend maintainer][projects]**. 1. If your merge request includes a new dependency or a filesystem change, it must - be **approved by a [Build team member][team]**. See [how to work with Build team][build handbook] for more details. + be **approved by a [Build team member][team]**. See [how to work with the Build team][build handbook] for more details. 1. To lower the amount of merge requests maintainers need to review, you can ask or assign any [reviewers][projects] for a first review. 1. If you need some guidance (e.g. it's your first merge request), feel free |