Skip to content

GitLab Importer fails to import when importing a group when an existing group with same name exist in the namespace

Summary

GitLab Importer fails to import a group into another group when a subgroup with the same name exists.

Steps to reproduce

  1. Create a top-level group and give it a name, for example, "Group A"
  2. Create another top-level group, for example, "Group 1". And in this group, create a subgroup with the same name as the group created in step 1. For example, "Group A"
  3. Using GitLab Importer, try to import the top-level group created in step 1 into the top-level group created in step 2. Following the examples, import "Group A" into "Group 1"
  4. And the import will fail

What is the current bug behavior?

Groups can't be migrated into another group if there is a clash in the subgroups.

What is the expected correct behavior?

GitLab importer should deal with clashing group names.

Relevant logs and/or screenshots

GroupNameClash

Possible fixes

During the group creation, GitLab Importer could handle clashing group names by appending a sulfix, for example, by adding a counter, like:

  • Group A
  • Group A (1)
  • Group A (2)