Option to skip membership import when creating with templates
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Creating projects from templates can now optionally skip copying its group's members as direct members.
Problem to solve
Per the below, all members that have access to a project template in a group are copied over as a direct member on a newly template-created project:
https://docs.gitlab.com/ee/user/admin_area/custom_project_templates.html Repository and database information that are copied over to each new project are identical to the data exported with the GitLab Project Import/Export.
https://docs.gitlab.com/ee/user/project/settings/import_export.html#important-notes Group members are exported as project members, as long as the user has maintainer or administrator access to the group where the exported project lives.
While the behavior may be useful in a standard export/import situation, it may be undesirable in template creation where the new project may need tight rules to start with (say, its immediate sub-group level access ONLY). The direct members getting copied over in this case causes a lot more members to appear on the new project than expected by the project creator or group maintainer.
Proposal
Provide a way to not preserve/copy the group/project membership listing when an "import" is done in context of a template-based project creation.