diff options
| author | Mike Lewis <mlewis@gitlab.com> | 2019-02-08 18:18:47 +0000 |
|---|---|---|
| committer | Mike Lewis <mlewis@gitlab.com> | 2019-02-08 18:18:47 +0000 |
| commit | a9326cfa279edf1ae6ffa7708cdd38ee78e48b76 (patch) | |
| tree | 7b8708e5eb450bf49f53de6401f68f10363d4ee2 | |
| parent | 30b4b42e2f06cd3a97395ceae4f533dfeebc0ecb (diff) | |
| download | gitlab-ce-a9326cfa279edf1ae6ffa7708cdd38ee78e48b76.tar.gz | |
Update Documentation section to include link to new Documentation Requirements section in docs
| -rw-r--r-- | .gitlab/issue_templates/Feature proposal.md | 7 |
1 files changed, 2 insertions, 5 deletions
diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md index 3cd800907a3..abfbef4b2b0 100644 --- a/.gitlab/issue_templates/Feature proposal.md +++ b/.gitlab/issue_templates/Feature proposal.md @@ -39,11 +39,8 @@ Existing personas are: (copy relevant personas out of this comment, and delete a ### Documentation -<!-- See the Documentation Workflows https://docs.gitlab.com/ee/development/documentation/workflow.html and specify the following: -What doc pages need to be created or updated across user, admin, and API docs? -What concepts, procedures, or information is needed in each area? Is there an 'old way' that should be deprecated in the docs? -If applicable, specify a new or updated feature name, description, benefits, and use cases, which may all be used in the documentation or features.yml. -Which use cases or scenarios would benefit from a set of instructions or a guide, whether unique to each use case or flexible enough to cover multiple use cases. --> +<!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html +Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### What does success look like, and how can we measure that? |