diff options
| author | Marcel Amirault <mamirault@gitlab.com> | 2019-08-30 02:25:44 +0000 |
|---|---|---|
| committer | Evan Read <eread@gitlab.com> | 2019-08-30 02:25:44 +0000 |
| commit | 513d3f58117cfaa9c24e1a354a72e1a5346e1109 (patch) | |
| tree | 0b8aa9f625315f57d43de2d2fb4663c8b69d477b /doc/user/project/pipelines | |
| parent | e348def82fde55f70de517f1c51bb7fdbb8be9fd (diff) | |
| download | gitlab-ce-513d3f58117cfaa9c24e1a354a72e1a5346e1109.tar.gz | |
Fix markdown in various docs
Clean up issues that may cause the docs-lint
test to fail, such as trailing whitespace, no
EOF newline, blockquotes, etc
Diffstat (limited to 'doc/user/project/pipelines')
| -rw-r--r-- | doc/user/project/pipelines/settings.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/user/project/pipelines/settings.md b/doc/user/project/pipelines/settings.md index 456209c2180..78b6d202b32 100644 --- a/doc/user/project/pipelines/settings.md +++ b/doc/user/project/pipelines/settings.md @@ -107,11 +107,11 @@ in the pipelines settings page. ### Removing color codes Some test coverage tools output with ANSI color codes that won't be -parsed correctly by the regular expression and will cause coverage -parsing to fail. +parsed correctly by the regular expression and will cause coverage +parsing to fail. If your coverage tool doesn't provide an option to disable color -codes in the output, you can pipe the output of the coverage tool through a +codes in the output, you can pipe the output of the coverage tool through a small one line script that will strip the color codes off. For example: |