In hosted systems, enterprises often have a need to share their own templates across teams. This feature allows an administrator to pick a project to be the instance-wide collection of file templates. These templates are then exposed to all users through the Web Editor while the project remains secure.
To select a project to serve as the custom template repository:
- On the left sidebar, select Search or go to.
- Select Admin Area.
- Select Settings > Templates.
- Expand Templates
- From the dropdown list, select the project to use as the template repository.
- Select Save changes.
- Add custom templates to the selected repository.
These templates cannot be used as a value of the
include:template key in
Templates must be added to a specific subdirectory in the repository, corresponding to the kind of template. The following types of custom templates are supported:
Each template must go in its respective subdirectory, have the correct extension and not be empty. So, the hierarchy should look like this:
|-- README.md |-- Dockerfile |-- custom_dockerfile.dockerfile |-- another_dockerfile.dockerfile |-- gitignore |-- custom_gitignore.gitignore |-- another_gitignore.gitignore |-- gitlab-ci |-- custom_gitlab-ci.yml |-- another_gitlab-ci.yml |-- LICENSE |-- custom_license.txt |-- another_license.txt
Your custom templates are displayed on the dropdown list when a new file is added through the GitLab UI:
If this feature is disabled or no templates are present, no Custom section displays in the selection dropdown.