Skip to content

Added GitLab tier upgrade section

Russell Dickenson requested to merge russell/add-subscription-upgrade-section into master

What does this MR do?

Moves GitLab subscription tier upgrade documentation into its own section, to make it easier to find.

The intent of this MR is to make it easier for a customer to upgrade to a higher GitLab tier. No useful information is contained in the UI. If a customer then searches for terms such as gitlab upgrade tier, amongst the top results is the Subscription docs. However, those docs contain very little detail about a tier upgrade, and are intermixed with other content. This MR aims to raise the profile of the tier upgrade instructions, both for GitLab.com customers, and self-managed customers.

To help direct customers to the correct documentation, https://gitlab.com/gitlab-org/growth/product/-/issues/286 has been raised to add a link the Subscription docs in the GitLab UI.

Related issues

Author's checklist

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.
  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