Skip to content

Commit 631f8b1

Browse files
Update publish-modules.mdx
1 parent b9081d6 commit 631f8b1

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/terraform-docs-common/docs/cloud-docs/registry/publish-modules.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ When the **Publish modules to your private registry from a single repository** o
8181

8282
By default, HCP Terraform and Terraform Enterprise retrieve new versions of modules published to the private registry according to the repository release tag. As a result, you must store the code for each module in separate repositories. Otherwise, the registry retrieves and publishes new versions of all modules in a repository each time you create a new release tag.
8383

84-
If you want to use a single repository to store modules source code, you can enable the **Publish modules to your private registry from a single repository** option in your workspace's general settings. When this option is enabled, you can add a prefix to the version tag that the registry uses to select module sources to publish when new you create new release tags. Refer to [Release tag prefixes](#release-tag-prefixes) for additional information.
84+
If you want to use a single repository to store modules source code, you can enable the **Publish modules to your private registry from a single repository** option in your organization's general settings. When this option is enabled, you can add a prefix to the version tag that the registry uses to select module sources to publish when new you create new release tags. Refer to [Release tag prefixes](#release-tag-prefixes) for additional information.
8585

8686
After enabling this option, complete the instructions for [publishing a new module](#publish-a-new-module).
8787

0 commit comments

Comments
 (0)