Skip to content

Remove most docs from ee_specific_check whitelist

Marcel Amirault requested to merge (removed):docs-ee-specific-check into master

What does this MR do?

The majority of docs have been aligned between CE and EE, and thus the majority of the directories can be removed from the ee_specific_check whitelist. This will close many MRs that became conflicted over time, and will close their related issues for the Single Docs codebase Epic.

Some docs did not align as expected, and these will be fixed shortly. In order to allow them to be corrected, their respective directories will not be removed from the whitelist here (yet). The docs that need to be checked (tomorrow, hopefully), as I verified myself locally, (and found in the Pretty Diff) are:

Note: gitlab-ce/doc/administration/geo/disaster_recovery/ and gitlab-ce/doc/administration/geo/replication/ should be fixed in: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28099

Note 2: doc/api will be aligned at a later time.

gitlab-ce/doc/administration/index.md gitlab-ee/doc/administration/index.md
gitlab-ce/doc/administration/operations/extra_sidekiq_processes.md gitlab-ee/doc/administration/operations/extra_sidekiq_processes.md
rics_reports.md
gitlab-ce/doc/development/geo.md gitlab-ee/doc/development/geo.md
gitlab-ce/doc/development/README.md gitlab-ee/doc/development/README.md
gitlab-ce/doc/README.md gitlab-ee/doc/README.md
gitlab-ce/doc/user/admin_area/geo_nodes.md gitlab-ee/doc/user/admin_area/geo_nodes.md
gitlab-ce/doc/user/application_security/dependency_scanning/index.md gitlab-ee/doc/user/application_security/dependency_scanning/index.md
gitlab-ce/doc/user/application_security/sast/index.md gitlab-ee/doc/user/application_security/sast/index.md
gitlab-ce/doc/user/project/labels.md gitlab-ee/doc/user/project/labels.md

Related issues

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/61073
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60841
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60838
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60845
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/59156
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/61272
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/61362
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/59151
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/61269

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 🤖 GitLab Bot 🤖

Merge request reports