Skip to content

Docs: Merge EE doc/​user/group to CE

Marcel Amirault requested to merge (removed):docs-repo-merge-10-group-misc into master

What does this MR do?

Ported to EE in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/11639

This aligns the CE and EE doc/user/group docs, as part of the effort to combine docs into a single codebase (&199 (closed)).

This MR (and the EE Port):

  • Brings in:
    • doc/​user/​group/​clusters
    • doc/​user/​group/​contribution_analytics
    • doc/​user/​group/​epics
    • doc/​user/​group
    • doc/​user/​group/​insights
    • doc/​user/​group/​issues_analytics
    • doc/​user/​group/​roadmap
    • doc/​user/​group/​saml_sso
    • doc/​user/​group/​security_dashboard
  • Images:
    • Brings 30 EE-only images into CE.
    • Deletes 3 orphaned images from EE (user/group/security_dashboard/img), and does not bring them into CE.
  • Changes relative links to absolute links as necessary.
  • Brings in changes to group docs that were done in EE, but never ported to CE (See https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/9754, https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8490, etc.)
  • Adds missing badges to user/group/issues_analytics/index.md and user/group/saml_sso/scim_setup.md

When both the EE Port and this MR are merged, the doc/user/group docs should hopefully be aligned between CE and EE.

Then, please merge: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/11875, and the issue will be closed.

Related issues

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/60850

Author's checklist

  • Follow the Documentation Guidelines and Style Guide.
  • 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 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.

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 and that you merge the equivalent EE MR before the CE MR if both exist.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Marcel Amirault

Merge request reports