Commit be4217a7 authored by Evan Read's avatar Evan Read

Merge branch 'docs-visibility-setting-gitlab-com' into 'master'

Docs update for visibility restriction on GitLab.com

Closes gitlab-ee#12501

See merge request gitlab-org/gitlab-ce!30203
parents 8cbe2027 e83222a6
...@@ -13,6 +13,12 @@ Constants for snippet visibility levels are: ...@@ -13,6 +13,12 @@ Constants for snippet visibility levels are:
| `internal` | The snippet is visible for any logged in user | | `internal` | The snippet is visible for any logged in user |
| `public` | The snippet can be accessed without any authentication | | `public` | The snippet can be accessed without any authentication |
NOTE: **Note:**
From July 2019, the `Internal` visibility setting is disabled for new projects, groups,
and snippets on GitLab.com. Existing projects, groups, and snippets using the `Internal`
visibility setting keep this setting. You can read more about the change in the
[relevant issue](https://gitlab.com/gitlab-org/gitlab-ee/issues/12388).
## List snippets ## List snippets
Get a list of project snippets. Get a list of project snippets.
......
...@@ -29,6 +29,12 @@ in users. ...@@ -29,6 +29,12 @@ in users.
Any logged in user will have [Guest permissions](../user/permissions.md) Any logged in user will have [Guest permissions](../user/permissions.md)
on the repository. on the repository.
NOTE: **Note:**
From July 2019, the `Internal` visibility setting is disabled for new projects, groups,
and snippets on GitLab.com. Existing projects, groups, and snippets using the `Internal`
visibility setting keep this setting. You can read more about the change in the
[relevant issue](https://gitlab.com/gitlab-org/gitlab-ee/issues/12388).
### Private projects ### Private projects
Private projects can only be cloned and viewed by project members. Private projects can only be cloned and viewed by project members.
......
...@@ -352,3 +352,13 @@ High Performance TCP/HTTP Load Balancer: ...@@ -352,3 +352,13 @@ High Performance TCP/HTTP Load Balancer:
[unicorn-worker-killer]: https://rubygems.org/gems/unicorn-worker-killer "unicorn-worker-killer" [unicorn-worker-killer]: https://rubygems.org/gems/unicorn-worker-killer "unicorn-worker-killer"
[4010]: https://gitlab.com/gitlab-com/infrastructure/issues/4010 "Find a good value for maximum timeout for Shared Runners" [4010]: https://gitlab.com/gitlab-com/infrastructure/issues/4010 "Find a good value for maximum timeout for Shared Runners"
[4070]: https://gitlab.com/gitlab-com/infrastructure/issues/4070 "Configure per-runner timeout for shared-runners-manager-X on GitLab.com" [4070]: https://gitlab.com/gitlab-com/infrastructure/issues/4070 "Configure per-runner timeout for shared-runners-manager-X on GitLab.com"
## Other admin area settings
This area highlights other noteworthy admin area settings on GitLab.com that differ from default settings. This list is not exhaustive.
NOTE: **Note:**
From July 2019, the `Internal` visibility setting is disabled for new projects, groups,
and snippets on GitLab.com. Existing projects, groups, and snippets using the `Internal`
visibility setting keep this setting. You can read more about the change in the
[relevant issue](https://gitlab.com/gitlab-org/gitlab-ee/issues/12388).
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment