Skip to content

Bring all EE-only API docs to CE

Achilleas Pipinellis requested to merge docs/ee-only-api-single-codebase into master

What does this MR do?

To further facilitate our last remaining items for the single codebase effort (API docs), let's bring over all the EE-only API docs which don't need any special treatment. Specifically:

  • doc/api/epic_issues.md
  • doc/api/epic_links.md
  • doc/api/epics.md
  • doc/api/geo_nodes.md
  • doc/api/issue_links.md
  • doc/api/license.md
  • doc/api/license_templates.md
  • doc/api/managed_licenses.md
  • doc/api/merge_request_approvals.md
  • doc/api/packages.md
  • doc/api/scim.md
  • doc/api/vulnerabilities.md

Related issues

Part of https://gitlab.com/gitlab-org/gitlab-ce/issues/60045

&199 (closed)

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.

Merge request reports