gitlab-org--gitlab-foss/.gitlab/merge_request_templates/Documentation.md

<!-- Follow the documentation workflow https://docs.gitlab.com/ee/development/documentation/workflow.html -->
<!-- Additional information is located at https://docs.gitlab.com/ee/development/documentation/ --> 

<!-- Mention "documentation" or "docs" in the MR title -->
<!-- For changing documentation location use the "Change documentation location" template -->

## What does this MR do?

<!-- Briefly describe what this MR is about. -->

## Related issues

<!-- Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it. -->

## Author's checklist

- [ ] Follow the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).
- [ ] Link docs to and from the higher-level index page, plus other related docs where helpful.
- [ ] Apply the ~Documentation label.

## Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).

**1. Primary Reviewer**

* [ ] Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
 
**2. Technical Writer**

* [ ] Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable [DevOps stage](https://about.gitlab.com/handbook/product/categories/#devops-stages).

**3. Maintainer**

1. [ ] Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
1. [ ] Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist.
1. [ ] If there has not been a technical writer review, [create an issue for one using the Doc Review template](https://gitlab.com/gitlab-org/gitlab-ce/issues/new?issuable_template=Doc%20Review).

/label ~Documentation
Update Documentation MR template 2019-01-10 23:04:02 -05:00			`<!-- Follow the documentation workflow https://docs.gitlab.com/ee/development/documentation/workflow.html -->`
			`<!-- Additional information is located at https://docs.gitlab.com/ee/development/documentation/ -->`
Documentation process at GitLab 2018-08-16 05:30:04 -04:00
			`<!-- Mention "documentation" or "docs" in the MR title -->`
Update Documentation MR template 2019-01-10 23:04:02 -05:00			`<!-- For changing documentation location use the "Change documentation location" template -->`
Add MR Documentation description template 2016-09-01 03:42:18 -04:00
			`## What does this MR do?`

Update Documentation MR template 2019-01-10 23:04:02 -05:00			`<!-- Briefly describe what this MR is about. -->`
Update the Documentation MR template [ci skip] 2018-03-27 03:41:15 -04:00
			`## Related issues`

Remove placeholder word Closes from Documentation MR template 2019-02-05 23:06:37 -05:00			`<!-- Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it. -->`
Add MR Documentation description template 2016-09-01 03:42:18 -04:00
Documentation process at GitLab 2018-08-16 05:30:04 -04:00			`## Author's checklist`

Updates to Documentation.md 2019-01-17 14:37:24 -05:00			`- [ ] Follow the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).`
Update Documentation template 2019-01-17 15:58:27 -05:00			`- [ ] Link docs to and from the higher-level index page, plus other related docs where helpful.`
Remove unnecessary mentions of milestone and EE vs CE 2019-02-07 15:52:44 -05:00			`- [ ] Apply the ~Documentation label.`
Documentation process at GitLab 2018-08-16 05:30:04 -04:00
			`## Review checklist`

Updates to Documentation.md 2019-01-17 14:37:24 -05:00			`All reviewers can help ensure accuracy, clarity, completeness, and adherence to the [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide.html).`

			`1. Primary Reviewer`

Update Documentation template 2019-01-17 15:58:27 -05:00			`* [ ] Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.`
Updates to Documentation.md 2019-01-17 14:37:24 -05:00
			`2. Technical Writer`

			`* [ ] Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable [DevOps stage](https://about.gitlab.com/handbook/product/categories/#devops-stages).`

			`3. Maintainer`

			`1. [ ] Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.`
Update Documentation MR template to remove most of the language around milestones 2019-02-07 21:53:58 -05:00			`1. [ ] Ensure a release milestone is set and that you merge the equivalent EE MR before the CE MR if both exist.`
			`1. [ ] If there has not been a technical writer review, [create an issue for one using the Doc Review template](https://gitlab.com/gitlab-org/gitlab-ce/issues/new?issuable_template=Doc%20Review).`
Update the Documentation MR template [ci skip] 2018-03-27 03:41:15 -04:00
			`/label ~Documentation`