blob: 7badd74826106db86c5c81b6b8c83f115b87d425 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
<!-- 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 "Closes" if merging this should automatically close it. -->
Closes
## Author's checklist
- [ ] Use the Style Guide, as needed. https://docs.gitlab.com/ee/development/documentation/styleguide.html
- [ ] Link the document to and from the higher-level index page.
- [ ] Link the document to and from other subject-related docs, as appropriate.
- [ ] Apply the Documentation label and intended milestone, if known.
- [ ] [Port the MR to EE (or backport from CE)](https://docs.gitlab.com/ee/development/documentation/index.html#cherry-picking-from-ce-to-ee): _always recommended, required when the `ee-compat-check` job fails_.
## Review checklist
- [ ] Optional review by a subject-matter expert, if the author has one in mind.
- [ ] Review by MR assignee for clarity and GitLab style (required).
- [ ] Technical writer review (optional). You can mention the writer listed for the applicable DevOps stage https://about.gitlab.com/handbook/product/categories/#devops-stages
- [ ] If EE and CE MRs exist, merge the EE MR first, then the CE MR.
- [ ] Merge.
- [ ] Mention the the technical writer listed for the applicable DevOps stage if they have not already reviewed.
/label ~Documentation
|
