Thanks for considering a contribution to GitLab's built-in project templates.
For contributing new project templates or updating exisiting ones, you will need to have
For new templates you will also need to ensure you have
If you are using the GitLab Development Kit (GDK) you will have to disable
praefect and regenerate the Procfile, as the rake task is not currently compatible with it.
# gitlab-development-kit/gdk.yml praefect: enabled: false
If you want to contribute to an existing GitLab Pages template, contribute to the corresponding project on https://gitlab.com/pages.
If you want to add a new template, create a public project and open an issue under https://gitlab.com/gitlab-org/gitlab for this project to be added to https://gitlab.com/pages.
If you'd like to contribute a new built-in project template to be distributed with GitLab, please do the following:
@mention the relevant Backend Engineering Manager and Product Manager for the Templates category.
To make the project template available when creating a new project, the vendoring process will have to be completed:
spec/lib/gitlab/project_template_spec.rb, in the test for the
gitlab/ee/spec/lib/gitlab/project_template_spec.rb, in the
$nameis the name you gave the template in
gitlab/vendor/project_templatesand remove the resulting build folders
bin/rake gettext:regeneratein the
gitlabproject and commit new
bin/changelog -m 25486 "Add Project template for .NET")
yarn run svgson
gitlab-svgsproject and commit result
gitlab-svgsproject to master. This involves:
masterto pick up the new svgs
Existing templates are available in the project-templates group.
To contribute a change, please open a merge request in the relevant project and mention @gitlab-org/manage/import/backend when you are ready for a review.
Then, if your merge request gets accepted, either open an issue on
gitlab to ask for it to get updated, or open a merge request updating
the vendored template using the command
as above, where
$name is the name of the template that you want to be updated.