Docs: Missing information about renaming GitLab groups (incl. top-level groups and subgroups)

• Start this issue's title with Docs: or Docs feedback:.

Problem to solve

There is currently no good documentation in GitLab describing the process, risks, and downstream effects of renaming a Group (which, in many organizations, represents the entire “org”). This includes top-level groups as well as subgroups containing multiple projects.

Further details

Renaming a Group changes the full path for:

• The group itself
• All subgroups
• All projects inside those groups

Can this lead to widespread impact across an entire organization? what are the steps to take and what to watch for?

Proposal

GitLab documentation currently does not provide:

• A detailed explanation of what renaming a Group affects
• A safe workflow or migration plan
• Expected redirects (what GitLab does and does not handle)
• Pre- and post-rename validation steps
• Best practices for large org/group renames

Please add:

• Step-by-step recommended procedure
  • Pre-rename checks
  • Performing the rename safely
  • What GitLab automatically redirects
  • What must be manually updated
• Post-rename validation
  • CI/CD verification
  • Registry access validation
  • Runner health check
  • API client validation

Who can address the issue

Other links/references

/groups