diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-01-20 15:11:06 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-01-20 15:11:06 +0300 |
| commit | f2ebc27236ecef67e67da1da864bbf58e9b9c267 (patch) | |
| tree | d6fccf4eec0dd09f1ad009cacbf157298fbecfec /doc/development/dangerbot.md | |
| parent | 8994750e4e1beb9f6d1b37c1625fba5868b9babf (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/dangerbot.md')
| -rw-r--r-- | doc/development/dangerbot.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/dangerbot.md b/doc/development/dangerbot.md index 59b31437161..413c0a31eec 100644 --- a/doc/development/dangerbot.md +++ b/doc/development/dangerbot.md @@ -105,9 +105,9 @@ minimize the number of lines of code in `danger/`. A non-trivial `Dangerfile` should mostly call plugin code with arguments derived from the methods provided by Danger. The plugin code itself should have unit tests. -At present, we do this by putting the code in a module in `lib/gitlab/danger/...`, +At present, we do this by putting the code in a module in `tooling/danger/...`, and including it in the matching `danger/plugins/...` file. Specs can then be -added in `spec/lib/gitlab/danger/...`. +added in `spec/tooling/danger/...`. To determine if your `Dangerfile` works, push the branch that contains it to GitLab. This can be quite frustrating, as it significantly increases the cycle |