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

3.7 KiB

What does this MR do?

Author's checklist (required)

  • Follow the Documentation Guidelines and Style Guide.
  • Apply the ~documentation label, plus:
    • The corresponding DevOps stage and group label, if applicable.
    • ~"development guidelines" when changing docs under doc/development/*, CONTRIBUTING.md, or README.md.
    • ~"development guidelines" and ~"Documentation guidelines" when changing docs under development/documentation/*.
    • ~"development guidelines" and ~"Description templates (.gitlab/*)" when creating/updating issue and MR description templates.
  • Assign the designated Technical Writer.

When applicable:

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

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.
    • Add ~"Technical Writing" and docs:: workflow label.
    • Add ~docs-only when the only files changed are under doc/*.

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.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

/label ~documentation