Skip to content

Add "top-level group" to misused terms in favor of "group"

Jeremy Watson (ex-GitLab) requested to merge jeremy-master-patch-36112 into master

Why is this change being made?

A "top-level group" is sometimes used to reference a group at the top of the group hierarchy on an instance (like gitlab-org on GitLab.com). Instead, we should just call these "groups" - if it wasn't at the top of the group hierarchy, it would be a subgroup.

Thanks to @ebrinkman for the inspiration.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • 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.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

Merge request reports