diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-27 15:06:30 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-27 15:06:30 +0300 |
| commit | 3269a20692c5b1f32862072d7897a4e753bae9ef (patch) | |
| tree | 9dfc6e7ccb857b323dc8b12259d339b76b8b90bf /danger/database | |
| parent | c02f53288a838166a28518983fae3b80ca5936d8 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'danger/database')
| -rw-r--r-- | danger/database/Dangerfile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/danger/database/Dangerfile b/danger/database/Dangerfile index fc6c5130fdc..56624c0b897 100644 --- a/danger/database/Dangerfile +++ b/danger/database/Dangerfile @@ -20,7 +20,7 @@ changes are reviewed, take the following steps: 1. Ensure the merge request has ~database and ~"database::review pending" labels. If the merge request modifies database files, Danger will do this for you. -1. Use the [Database changes checklist](https://gitlab.com/gitlab-org/gitlab-foss/blob/master/.gitlab/merge_request_templates/Database%20changes.md) +1. Use the [Database changes checklist](https://gitlab.com/gitlab-org/gitlab/blob/master/.gitlab/merge_request_templates/Database%20changes.md) template or add the appropriate items to the MR description. 1. Assign and mention the database reviewer suggested by Reviewer Roulette. MSG |