Group-level project templates
Problem to solve
Especially in larger projects, setting up new GitLab projects from scratch can be a repetitive task. Often, there is a lot of configuration files and boilerplate required.
We already have project templates, but these are GitLab-owned and cannot be customized. A solution to set up project templates based on actual GitLab projects is needed.
Relevant use cases for project templates on group-level:
- Unchanged, default templates only (you have vendored templates only)
- As an admin, add your own templates based on a selected group (have both vendored and custom)
- Add own templates and disabled vendored ones (you have only what you need)
- Disable vendored templates (same effect as disable templates)
- Group master can select a sub-group that contains project templates
- Users when creating a new project will see group templates from every group they have permissions to create a new project in, instance templates and vendor templates
to be updated after Product Discovery
What does success look like, and how can we measure that?
- If a template group is defined, projects inside this group are made available as project templates when creating a new project.