Skip to content

Docs: Merge EE doc/user/project/*.md to CE

Marcel Amirault requested to merge (removed):docs-repo-merge-26-project-misc into master

What does this MR do?

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

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

This MR:

  • Brings in EE only files:
    • doc/user/project/canary_deployments.md
    • doc/user/project/ci_cd_for_external_repo.md
    • doc/user/project/code_owners.md
    • doc/user/project/deploy_boards.md
    • doc/user/project/file_lock.md
    • doc/user/project/maven_packages.md
    • doc/user/project/security_dashboard.md
    • doc/user/project/service_desk.md
  • Brings EE only information into:
    • doc/user/project/description_templates.md
    • doc/user/project/index.md
    • doc/user/project/labels.md
    • doc/user/project/protected_branches.md
    • doc/user/project/quick_actions.md
  • Brings in 22 images related to the docs above.
  • Updates relative links to absolute, and adds badges, as necessary.

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

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

Related issues

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

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