diff options
| -rw-r--r-- | doc/administration/pages/index.md | 1 | ||||
| -rw-r--r-- | doc/ci/environments/index.md | 2 | ||||
| -rw-r--r-- | doc/user/application_security/index.md | 2 | ||||
| -rw-r--r-- | doc/user/application_security/sast/index.md | 5 |
4 files changed, 5 insertions, 5 deletions
diff --git a/doc/administration/pages/index.md b/doc/administration/pages/index.md index 8a0d3f552bf..01a71db018f 100644 --- a/doc/administration/pages/index.md +++ b/doc/administration/pages/index.md @@ -237,6 +237,7 @@ control over how the Pages daemon runs and serves content in your environment. | `log_verbose` | Verbose logging, true/false. | | `propagate_correlation_id` | Set to true (false by default) to re-use existing Correlation ID from the incoming request header `X-Request-ID` if present. If a reverse proxy sets this header, the value is propagated in the request chain. | | `max_connections` | Limit on the number of concurrent connections to the HTTP, HTTPS or proxy listeners. | +| `max_uri_length` | The maximum length of URIs accepted by GitLab Pages. Set to 0 for unlimited length. [Introduced](https://gitlab.com/gitlab-org/gitlab-pages/-/issues/659) in GitLab 14.5. | `metrics_address` | The address to listen on for metrics requests. | | `redirect_http` | Redirect pages from HTTP to HTTPS, true/false. | | `sentry_dsn` | The address for sending Sentry crash reporting to. | diff --git a/doc/ci/environments/index.md b/doc/ci/environments/index.md index 6d0f0a7e6f1..c6fa63af2b7 100644 --- a/doc/ci/environments/index.md +++ b/doc/ci/environments/index.md @@ -159,9 +159,9 @@ deploy_prod: environment: name: production url: https://example.com - when: manual rules: - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH + when: manual ``` The `when: manual` action: diff --git a/doc/user/application_security/index.md b/doc/user/application_security/index.md index c595b228337..d5e801ced9c 100644 --- a/doc/user/application_security/index.md +++ b/doc/user/application_security/index.md @@ -226,7 +226,7 @@ To enable or edit the Vulnerability-Check rule: 1. On the top bar, select **Menu > Projects** and find your project. 1. On the left sidebar, select **Settings > General**. 1. Expand **Merge request approvals**. -1. Select **Enable** or **Edit**. +1. Select **Activate** or **Edit** of the Vulnerability-Check. 1. Complete the fields. **Approvals required** must be at least 1. 1. Select **Add approval rule**. diff --git a/doc/user/application_security/sast/index.md b/doc/user/application_security/sast/index.md index 720140418a0..af8585c6a18 100644 --- a/doc/user/application_security/sast/index.md +++ b/doc/user/application_security/sast/index.md @@ -16,9 +16,8 @@ explains how 4 of the top 6 attacks were application based. Download it to learn organization. If you're using [GitLab CI/CD](../../../ci/index.md), you can use Static Application Security -Testing (SAST) to check your source code for known vulnerabilities. When a pipeline completes, -the results of the SAST analysis are processed and shown in the pipeline's Security tab. If the -pipeline is associated with a merge request, the SAST analysis is compared with the results of +Testing (SAST) to check your source code for known vulnerabilities. +If the pipeline is associated with a merge request, the SAST analysis is compared with the results of the target branch's analysis (if available). The results of that comparison are shown in the merge request. If the pipeline is running from the default branch, the results of the SAST analysis are available in the [security dashboards](../security_dashboard/index.md). |