diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-12-26 21:07:49 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-12-26 21:07:49 +0000 |
| commit | b558264c9d10841f46a8ffeb15f18d0cee60fa7a (patch) | |
| tree | 48733878d8c1351038ec21146dadef50a86b14b4 /danger | |
| parent | 3677c80c9b40d5b412cbbe127510a7d7b975a8e7 (diff) | |
| download | gitlab-ce-b558264c9d10841f46a8ffeb15f18d0cee60fa7a.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'danger')
| -rw-r--r-- | danger/database/Dangerfile | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/danger/database/Dangerfile b/danger/database/Dangerfile index 56624c0b897..16740cb867d 100644 --- a/danger/database/Dangerfile +++ b/danger/database/Dangerfile @@ -20,8 +20,8 @@ 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/blob/master/.gitlab/merge_request_templates/Database%20changes.md) - template or add the appropriate items to the MR description. +1. Prepare your MR for database review according to the + [docs](https://docs.gitlab.com/ee/development/database_review.html#how-to-prepare-the-merge-request-for-a-database-review). 1. Assign and mention the database reviewer suggested by Reviewer Roulette. MSG |