Commit 4b339d80 authored by Craig Norris's avatar Craig Norris

Remove outdated GitLab version refs from doc pages

Remove outdated GitLab version refs from doc pages
parent 422d1187
...@@ -603,8 +603,8 @@ For monitoring deployed apps, see [Jaeger tracing documentation](../operations/t ...@@ -603,8 +603,8 @@ For monitoring deployed apps, see [Jaeger tracing documentation](../operations/t
- Layer: Core Service - Layer: Core Service
- Process: `logrotate` - Process: `logrotate`
GitLab is comprised of a large number of services that all log. We started bundling our own Logrotate GitLab is comprised of a large number of services that all log. We bundle our own Logrotate
as of GitLab 7.4 to make sure we were logging responsibly. This is just a packaged version of the common open source offering. to make sure we were logging responsibly. This is just a packaged version of the common open source offering.
#### Mattermost #### Mattermost
......
...@@ -141,8 +141,7 @@ Feature.disable(:reject_unsigned_commits_by_gitlab) ...@@ -141,8 +141,7 @@ Feature.disable(:reject_unsigned_commits_by_gitlab)
## Prevent pushing secrets to the repository ## Prevent pushing secrets to the repository
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/385) in GitLab 8.12. > Moved to GitLab Premium in 13.9.
> - Moved to GitLab Premium in 13.9.
Secrets such as credential files, SSH private keys, and other files containing secrets should never be committed to source control. Secrets such as credential files, SSH private keys, and other files containing secrets should never be committed to source control.
GitLab enables you to turn on a predefined denylist of files which can't be GitLab enables you to turn on a predefined denylist of files which can't be
...@@ -217,8 +216,7 @@ id_ecdsa ...@@ -217,8 +216,7 @@ id_ecdsa
## Prohibited file names ## Prohibited file names
> - Introduced in GitLab 7.10. > Moved to GitLab Premium in 13.9.
> - Moved to GitLab Premium in 13.9.
Each filename contained in a Git push is compared to the regular expression in this field. Filenames in Git consist of both the file's name and any directory that may precede it. A singular regular expression can contain multiple independent matches used as exclusions. File names can be broadly matched to any location in the repository, or restricted to specific locations. Filenames can also be partial matches used to exclude file types by extension. Each filename contained in a Git push is compared to the regular expression in this field. Filenames in Git consist of both the file's name and any directory that may precede it. A singular regular expression can contain multiple independent matches used as exclusions. File names can be broadly matched to any location in the repository, or restricted to specific locations. Filenames can also be partial matches used to exclude file types by extension.
......
...@@ -122,15 +122,11 @@ email addresses to disallowed domains after sign up. ...@@ -122,15 +122,11 @@ email addresses to disallowed domains after sign up.
### Allowlist email domains ### Allowlist email domains
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/598) in GitLab 7.11.0
You can restrict users only to sign up using email addresses matching the given You can restrict users only to sign up using email addresses matching the given
domains list. domains list.
### Denylist email domains ### Denylist email domains
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5259) in GitLab 8.10.
You can block users from signing up when using an email addresses of specific domains. This can You can block users from signing up when using an email addresses of specific domains. This can
reduce the risk of malicious users creating spam accounts with disposable email addresses. reduce the risk of malicious users creating spam accounts with disposable email addresses.
......
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