diff options
| author | Seth Berger <4310743-sethgitlab@users.noreply.gitlab.com> | 2019-09-12 03:49:57 +0300 |
|---|---|---|
| committer | Seth Berger <4310743-sethgitlab@users.noreply.gitlab.com> | 2019-09-12 03:49:57 +0300 |
| commit | 7d2c2cc3c52c1180cfc1a7b67d94bbd4fac06a23 (patch) | |
| tree | 84bff447f681e46e963fbafe41005ec570a683c1 | |
| parent | 17451e8ce8bff057db17411f0b61572c8fa3d9b4 (diff) | |
Apply suggestion to doc/development/documentation/feature-change-workflow.md
| -rw-r--r-- | doc/development/documentation/feature-change-workflow.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/documentation/feature-change-workflow.md b/doc/development/documentation/feature-change-workflow.md index 99cd474e9bb..69a050d85e0 100644 --- a/doc/development/documentation/feature-change-workflow.md +++ b/doc/development/documentation/feature-change-workflow.md @@ -95,7 +95,7 @@ do the following: As a developer, if a ~feature issue also contains the ~Documentation label, you must ship the new or updated documentation with the code of the feature. The documentation is an essential part of the product. Technical writers are happy to help, as requested and planned on an issue-by-issue basis. -Follow the process below unless otherwise agreed with the product manager and technical writer for a given issue: +For feature issues requiring documentation, follow the process below unless otherwise agreed with the product manager and technical writer for a given issue: - Include any new and edited docs in the MR introducing the code. - Use the Documentation requirements confirmed by the Product Manager in the |