This article explains how group names work in the GitLab integration configuration and provides guidance on when and why you might want to specify them.
Group names are an optional field in the GitLab integration configuration. If you leave this field unspecified, the integration will automatically attempt to pull projects from all groups by default.
Specifying group names in your GitLab integration serves an important purpose:
It helps pull only relevant projects based on the groups they are assigned to
It prevents pulling unnecessary information into your catalog
It allows you to focus the integration on specific project groups that matter to your workflow
Consider specifying group names when:
You only need projects from specific GitLab groups
You want to reduce the amount of data pulled into your catalog
You need to focus on particular project groups for organizational purposes
You might want to leave group names unspecified when:
You need access to projects across all groups
You're setting up an initial integration and want to see all available projects
Group names in the GitLab integration configuration are optional. Specifying them helps filter which projects are pulled into your catalog, while leaving them blank will pull projects from all groups. Choose the approach that best fits your organizational needs.