diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-03 18:10:02 +0000 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-03 18:10:02 +0000 |
commit | 49058851264455c22a5ba00c8671b7d4cdfd8ee9 (patch) | |
tree | 6626f6610b69b418cea728edb1d804c79e189d29 /doc | |
parent | f397d486bc77b286d42f83b89e0879428c05299d (diff) | |
download | gitlab-ce-49058851264455c22a5ba00c8671b7d4cdfd8ee9.tar.gz |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc')
-rw-r--r-- | doc/development/documentation/styleguide/index.md | 4 | ||||
-rw-r--r-- | doc/user/packages/container_registry/index.md | 19 |
2 files changed, 21 insertions, 2 deletions
diff --git a/doc/development/documentation/styleguide/index.md b/doc/development/documentation/styleguide/index.md index 883f7d00185..792b64c318b 100644 --- a/doc/development/documentation/styleguide/index.md +++ b/doc/development/documentation/styleguide/index.md @@ -320,7 +320,7 @@ create an issue or an MR to propose a change to the user interface text. - *Feature names are typically lowercase*. - *Some features are capitalized*, typically nouns naming GitLab-specific capabilities or tools. - + See the [word list](word_list.md) for details. If the term is not in the word list, ask a GitLab Technical Writer for advice. @@ -839,7 +839,7 @@ We include guidance for links in these categories: ### Basic link criteria - Use inline link Markdown markup `[Text](https://example.com)`. - It's easier to read, review, and maintain. _Do not_ use `[Text][identifier]`. + It's easier to read, review, and maintain. _Do not_ use `[Text][identifier]` reference-style links. - Use [meaningful anchor texts](https://www.futurehosting.com/blog/links-should-have-meaningful-anchor-text-heres-why/). For example, instead of writing something like `Read more about GitLab Issue Boards [here](LINK)`, diff --git a/doc/user/packages/container_registry/index.md b/doc/user/packages/container_registry/index.md index 3acb9545cec..4bf86e0a6d4 100644 --- a/doc/user/packages/container_registry/index.md +++ b/doc/user/packages/container_registry/index.md @@ -745,6 +745,25 @@ You can, however, remove the Container Registry for a project: The **Packages & Registries > Container Registry** entry is removed from the project's sidebar. +## Set visibility of the Container Registry + +By default, the Container Registry is visible to everyone with access to the project. +You can, however, change the visibility of the Container Registry for a project: + +1. Go to your project's **Settings > General** page. +1. Expand the section **Visibility, project features, permissions**. +1. Under **Container Registry**, select an option from the dropdown: + + - **Everyone With Access** (Default): The Container Registry is visible to everyone with access + to the project. If the project is public, the Container Registry is also public. If the project + is internal or private, the Container Registry is also internal or private. + + - **Only Project Members**: The Container Registry is visible only to project members with + Reporter role or higher. This is similar to the behavior of a private project with Container + Registry visibility set to **Everyone With Access**. + +1. Select **Save changes**. + ## Manifest lists and garbage collection Manifest lists are commonly used for creating multi-architecture images. If you rely on manifest |