diff options
| author | Eddie Stubbington <eddiestubbington@icloud.com> | 2018-05-30 11:12:09 +0000 |
|---|---|---|
| committer | Marin Jankovski <marin@gitlab.com> | 2018-05-30 11:12:09 +0000 |
| commit | 146279b53a1b253bd75eee4b3ed37ebc8405b25b (patch) | |
| tree | b4cbf9c2356ba197f693f237e95147d1994d9a6d | |
| parent | 0956c86069b11bf4a1ea7485aac1b621eee7e157 (diff) | |
| download | gitlab-ce-146279b53a1b253bd75eee4b3ed37ebc8405b25b.tar.gz | |
Fixed broken link to build team in documentation
| -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 d03b7fa23ca..23c80799235 100644 --- a/doc/development/code_review.md +++ b/doc/development/code_review.md @@ -22,7 +22,7 @@ There are a few rules to get your merge request accepted: 1. If your merge request includes UX, frontend and backend changes [^1], it must be **approved by a [UX team member, a frontend and a backend maintainer][team]**. 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 the Build team][build handbook] for more details. + be *approved by a [Distribution team member][team]*. See how to work with the [Distribution team for more details.](https://about.gitlab.com/handbook/engineering/dev-backend/distribution/) 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 |