diff options
| author | Seth Berger <4310743-sethgitlab@users.noreply.gitlab.com> | 2019-09-12 03:47:39 +0300 |
|---|---|---|
| committer | Seth Berger <4310743-sethgitlab@users.noreply.gitlab.com> | 2019-09-12 03:47:39 +0300 |
| commit | 17451e8ce8bff057db17411f0b61572c8fa3d9b4 (patch) | |
| tree | 2f6e3c574a272cea8846d83e1f49afe88a0d12da | |
| parent | cf6d467de5cbb8d2c88944b82d7dae28d58cb519 (diff) | |
Apply suggestion to doc/development/documentation/feature-change-workflow.md
| -rw-r--r-- | doc/development/documentation/feature-change-workflow.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/development/documentation/feature-change-workflow.md b/doc/development/documentation/feature-change-workflow.md index 3dae4ca2518..99cd474e9bb 100644 --- a/doc/development/documentation/feature-change-workflow.md +++ b/doc/development/documentation/feature-change-workflow.md @@ -92,8 +92,7 @@ do the following: #### Authoring -As a developer, you should ship the documentation with the code of the feature that -you are creating or updating. The documentation is an essential part of the product. +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: |