diff options
| author | Marcel Amirault <mamirault@gitlab.com> | 2019-09-09 05:02:46 +0000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-09-09 05:02:46 +0000 |
| commit | bd58c2e00b97f7eee3a548d3bd4da54cacf3b88b (patch) | |
| tree | 72da16955413f9e3a78bf4d621077dfe861172e5 | |
| parent | 154f474bca2c432cdd2778de111a94191b537aa4 (diff) | |
| download | gitlab-ce-bd58c2e00b97f7eee3a548d3bd4da54cacf3b88b.tar.gz | |
Bring typo fix from EE into CE
| -rw-r--r-- | doc/development/dangerbot.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/dangerbot.md b/doc/development/dangerbot.md index 5fc5886e3a2..6bf59209d21 100644 --- a/doc/development/dangerbot.md +++ b/doc/development/dangerbot.md @@ -77,7 +77,7 @@ complex logic related to that task. Danger code is just Ruby code. It should adhere to our coding standards, and needs tests, like any other piece of Ruby in our codebase. However, we aren't -able to test a `Dangerfile` directly! So, to maximise test coverage, try to +able to test a `Dangerfile` directly! So, to maximize test coverage, try to 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. |