Commit 917d4933 authored by Brendan O'Leary 🐢's avatar Brendan O'Leary 🐢

Add why blocking secret file push is important

parent f0cfb07c
...@@ -90,8 +90,8 @@ GitLab uses [RE2 syntax](https://github.com/google/re2/wiki/Syntax) for regular ...@@ -90,8 +90,8 @@ GitLab uses [RE2 syntax](https://github.com/google/re2/wiki/Syntax) for regular
> [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/385) in [GitLab Starter](https://about.gitlab.com/pricing/) 8.12. > [Introduced](https://gitlab.com/gitlab-org/gitlab/issues/385) in [GitLab Starter](https://about.gitlab.com/pricing/) 8.12.
You can turn on a predefined blacklist of files which won't be allowed to be Secrets such as credential files, SSH private keys, and other files containing secrets should never be committed to source control. GitLab allows you to turn on a predefined blacklist of files which won't be allowed to be
pushed to a repository. pushed to a repository, stopping those commits from reaching the remote repository.
By selecting the checkbox *Prevent committing secrets to Git*, GitLab prevents By selecting the checkbox *Prevent committing secrets to Git*, GitLab prevents
pushes to the repository when a file matches a regular expression as read from pushes to the repository when a file matches a regular expression as read from
......
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