Commit 32f44cb1 authored by Evan Read's avatar Evan Read Committed by Achilleas Pipinellis

Edit new text on visibility setting

parent 1b3ebb4a
...@@ -353,12 +353,10 @@ High Performance TCP/HTTP Load Balancer: ...@@ -353,12 +353,10 @@ High Performance TCP/HTTP Load Balancer:
[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 ## Group and project settings
This area highlights other noteworthy admin area settings on GitLab.com that differ from default settings. This list is not exhaustive. On GitLab.com, projects, groups, and snippets created
after July 2019 have the `Internal` visibility setting disabled.
NOTE: **Note:** You can read more about the change in the
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). [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