summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2019-06-18 11:09:13 +1000
committerEvan Read <eread@gitlab.com>2019-06-18 11:09:13 +1000
commit1145c302f273084933bcc5edebb9c1f2d22ce6b7 (patch)
tree2129f8fb1cc22118e10ccd45369ba4b45484e18a
parent1276ff85453c6331e53f79680627c981b5ef00f7 (diff)
downloadgitlab-ce-docs/clarify-group-project-templates.tar.gz
Make group-level project template docs clearerdocs/clarify-group-project-templates
-rw-r--r--doc/user/group/custom_project_templates.md18
1 files changed, 11 insertions, 7 deletions
diff --git a/doc/user/group/custom_project_templates.md b/doc/user/group/custom_project_templates.md
index aa088d2fcdb..60f1328375e 100644
--- a/doc/user/group/custom_project_templates.md
+++ b/doc/user/group/custom_project_templates.md
@@ -9,13 +9,20 @@ type: reference
When you create a new [project](../project/index.md), creating it based on custom project templates is
a convenient bootstrap option.
+When a group-level project template is used, the following is copied into new
+projects:
+
+- Project settings.
+- Project files.
+
+This is in contrast to
+[instance-level project templates](../admin_area/custom_project_templates.md),
+which copy data as if GitLab's project
+[Import/Export feature](../project/settings/import_export.md) was used.
+
Users can configure a GitLab group that serves as template
source under a group's **Settings > General > Custom project templates**.
-NOTE: **Note:**
-GitLab administrators can
-[set project templates for an entire GitLab instance](../admin_area/custom_project_templates.md).
-
Within this section, you can configure the group where all the custom project
templates are sourced. Every project directly under the group namespace will be
available to the user if they have access to them. For example, every public
@@ -26,9 +33,6 @@ However, private projects will be available only if the user is a member of the
NOTE: **Note:**
Projects of nested subgroups of a selected template source cannot be used.
-Repository and database information that are copied over to each new project are
-identical to the data exported with [GitLab's Project Import/Export](../project/settings/import_export.md).
-
<!-- ## Troubleshooting
Include any troubleshooting steps that you can foresee. If you know beforehand what issues