You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{/* WARNING: This section is auto-generated during releases. Do not edit manually. */}
190
-
{/* Last updated: 2025-09-03T21:51:28Z via sourcegraph/sourcegraph@v6.7.2518*/}
190
+
{/* Last updated: 2025-09-18T21:46:05Z via sourcegraph/sourcegraph@v6.8.0*/}
191
191
```json
192
192
{
193
193
// If non-null, enforces GitLab repository permissions. This requires that there be an item in the `auth.providers` field of type "gitlab" with the same `url` field as specified in this `GitLabConnection`.
@@ -197,7 +197,7 @@ See [Internal rate limits](/admin/code_hosts/rate_limits#internal-rate-limits).
197
197
}
198
198
},
199
199
200
-
// TLS certificate of the GitLab instance. This is only necessary if the certificate is self-signed or signed by an internal CA. To get the certificate run `openssl s_client -connect HOST:443 -showcerts < /dev/null 2> /dev/null | openssl x509 -outform PEM`. To escape the value into a JSON string, you may want to use a tool like https://json-escape-text.now.sh.
200
+
// DEPRECATED: Use the tls.external setting in site config instead. TLS certificate of the GitLab instance. This is only necessary if the certificate is self-signed or signed by an internal CA. To get the certificate run `openssl s_client -connect HOST:443 -showcerts < /dev/null 2> /dev/null | openssl x509 -outform PEM`. To escape the value into a JSON string, you may want to use a tool like https://json-escape-text.now.sh.
0 commit comments