Skip to content

Fix relative urls after migration that originally pointed to about.gitlab.com

Michael Friedrich requested to merge fix-relative-urls into main

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

After the migration to the new handbook, the FQDN for the handbook changed from about.gitlab.com to handbook.gitlab.com . All relative URLs starting with / which are still hosted on about.gitlab.com, throw a 404 error in the handbook currently. Impacted divisions: Marketing, Engineering, Support, Product, Sales, Legal but also spans across multiple high frequent handbook pages such as Company.

Reviewing this MR will require lots of approvals based on the CodeOwner locations. Please do a high-level review with a selected handbook you maintain: The MR diff only changes relative URLs and fixes trailing whitespaces.

This MR fixes the URL errors, based on the analysis in #152 (comment 1785763437) with the following changelog:

fixes #152 (closed) related to &10

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
Edited by Michael Friedrich

Merge request reports