# Application settings API
> 原文:[https://docs.gitlab.com/ee/api/settings.html](https://docs.gitlab.com/ee/api/settings.html)
* [Get current application settings](#get-current-application-settings)
* [Change application settings](#change-application-settings)
* [List of settings that can be accessed via API calls](#list-of-settings-that-can-be-accessed-via-api-calls)
# Application settings API[](#application-settings-api-core-only "Permalink")
这些 API 调用使您可以阅读和修改`/admin/application_settings/general`显示的 GitLab 实例[应用程序设置](#list-of-settings-that-can-be-accessed-via-api-calls) . 您必须是管理员才能执行此操作.
## Get current application settings[](#get-current-application-settings "Permalink")
列出 GitLab 实例的当前[应用程序设置](#list-of-settings-that-can-be-accessed-via-api-calls) .
```
GET /application/settings
```
```
curl --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings"
```
响应示例:
```
{ "default_projects_limit" : 100000, "signup_enabled" : true, "id" : 1, "default_branch_protection" : 2, "restricted_visibility_levels" : [], "password_authentication_enabled_for_web" : true, "after_sign_out_path" : null, "max_attachment_size" : 10, "max_import_size": 50, "user_oauth_applications" : true, "updated_at" : "2016-01-04T15:44:55.176Z", "session_expire_delay" : 10080, "home_page_url" : null, "default_snippet_visibility" : "private", "outbound_local_requests_whitelist": [], "domain_whitelist" : [], "domain_blacklist_enabled" : false, "domain_blacklist" : [], "created_at" : "2016-01-04T15:44:55.176Z", "default_ci_config_path" : null, "default_project_visibility" : "private", "default_group_visibility" : "private", "gravatar_enabled" : true, "sign_in_text" : null, "container_expiration_policies_enable_historic_entries": true, "container_registry_token_expire_delay": 5, "repository_storages_weighted": {"default": 100}, "plantuml_enabled": false, "plantuml_url": null, "terminal_max_session_time": 0, "polling_interval_multiplier": 1.0, "rsa_key_restriction": 0, "dsa_key_restriction": 0, "ecdsa_key_restriction": 0, "ed25519_key_restriction": 0, "first_day_of_week": 0, "enforce_terms": true, "terms": "Hello world!", "performance_bar_allowed_group_id": 42, "instance_statistics_visibility_private": false, "user_show_add_ssh_key_message": true, "local_markdown_version": 0, "allow_local_requests_from_hooks_and_services": true, "allow_local_requests_from_web_hooks_and_services": true, "allow_local_requests_from_system_hooks": false, "asset_proxy_enabled": true, "asset_proxy_url": "https://assets.example.com", "asset_proxy_whitelist": ["example.com", "*.example.com", "your-instance.com"], "npm_package_requests_forwarding": true, "snippet_size_limit": 52428800, "issues_create_limit": 300, "raw_blob_request_limit": 300, "wiki_page_max_content_bytes": 52428800 }
```
在 GitLab 用户[高级版或旗舰](https://about.gitlab.com/pricing/)也可以看到`file_template_project_id` , `deletion_adjourned_period` ,或`geo_node_allowed_ips`参数:
```
{ "id" : 1, "signup_enabled" : true, "file_template_project_id": 1, "geo_node_allowed_ips": "0.0.0.0/0, ::/0", "deletion_adjourned_period": 7, ... }
```
## Change application settings[](#change-application-settings "Permalink")
使用 API调用来修改 GitLab 实例[应用程序设置](#list-of-settings-that-can-be-accessed-via-api-calls) .
```
PUT /application/settings
```
```
curl --request PUT --header "PRIVATE-TOKEN: <your_access_token>" "https://gitlab.example.com/api/v4/application/settings?signup_enabled=false&default_project_visibility=internal"
```
响应示例:
```
{ "id": 1, "default_projects_limit": 100000, "signup_enabled": false, "password_authentication_enabled_for_web": true, "gravatar_enabled": true, "sign_in_text": "", "created_at": "2015-06-12T15:51:55.432Z", "updated_at": "2015-06-30T13:22:42.210Z", "home_page_url": "", "default_branch_protection": 2, "restricted_visibility_levels": [], "max_attachment_size": 10, "max_import_size": 50, "session_expire_delay": 10080, "default_ci_config_path" : null, "default_project_visibility": "internal", "default_snippet_visibility": "private", "default_group_visibility": "private", "outbound_local_requests_whitelist": [], "domain_whitelist": [], "domain_blacklist_enabled" : false, "domain_blacklist" : [], "external_authorization_service_enabled": true, "external_authorization_service_url": "https://authorize.me", "external_authorization_service_default_label": "default", "external_authorization_service_timeout": 0.5, "user_oauth_applications": true, "after_sign_out_path": "", "container_registry_token_expire_delay": 5, "repository_storages": ["default"], "plantuml_enabled": false, "plantuml_url": null, "terminal_max_session_time": 0, "polling_interval_multiplier": 1.0, "rsa_key_restriction": 0, "dsa_key_restriction": 0, "ecdsa_key_restriction": 0, "ed25519_key_restriction": 0, "first_day_of_week": 0, "enforce_terms": true, "terms": "Hello world!", "performance_bar_allowed_group_id": 42, "instance_statistics_visibility_private": false, "user_show_add_ssh_key_message": true, "file_template_project_id": 1, "local_markdown_version": 0, "asset_proxy_enabled": true, "asset_proxy_url": "https://assets.example.com", "asset_proxy_whitelist": ["example.com", "*.example.com", "your-instance.com"], "geo_node_allowed_ips": "0.0.0.0/0, ::/0", "allow_local_requests_from_hooks_and_services": true, "allow_local_requests_from_web_hooks_and_services": true, "allow_local_requests_from_system_hooks": false, "npm_package_requests_forwarding": true, "snippet_size_limit": 52428800, "issues_create_limit": 300, "raw_blob_request_limit": 300, "wiki_page_max_content_bytes": 52428800 }
```
使用 GitLab [Premium 或 Ultimate 的](https://about.gitlab.com/pricing/)用户可能还会看到以下参数:
* `file_template_project_id`
* `geo_node_allowed_ips`
* `geo_status_timeout`
* `deletion_adjourned_period`
响应示例:
```
"file_template_project_id": 1, "geo_node_allowed_ips": "0.0.0.0/0, ::/0"
```
## List of settings that can be accessed via API calls[](#list-of-settings-that-can-be-accessed-via-api-calls "Permalink")
通常,所有设置都是可选的. 但是,如果启用了某些设置,则需要设置其他设置才能正常运行. 这些要求在相关设置的说明中列出.
| Attribute | Type | Required | Description |
| --- | --- | --- | --- |
| `admin_notification_email` | string | no | 如果设置了滥用报告,它将发送到该地址. 滥用报告始终在管理区域中可用. |
| `after_sign_out_path` | string | no | 注销后将用户重定向到的位置. |
| `after_sign_up_text` | string | no | 注册后向用户显示的文字 |
| `akismet_api_key` | string | 要求: `akismet_enabled` | Akismet 垃圾邮件防护的 API 密钥. |
| `akismet_enabled` | boolean | no | ( **如果启用,则要求:** `akismet_api_key` )启用或禁用 Akismet 垃圾邮件防护. |
| `allow_group_owners_to_manage_ldap` | boolean | no | 设置为`true`以允许组所有者管理 LDAP |
| `allow_local_requests_from_hooks_and_services` | boolean | no | (不建议使用:改用`allow_local_requests_from_web_hooks_and_services` )允许从挂钩和服务到本地网络的请求. |
| `allow_local_requests_from_system_hooks` | boolean | no | 允许从系统挂钩向本地网络发出请求. |
| `allow_local_requests_from_web_hooks_and_services` | boolean | no | 允许从 Web 挂钩和服务到本地网络的请求. |
| `archive_builds_in_human_readable` | string | no | 设置将作业视为过期和过期的持续时间. 一旦超过该时间,作业将被存档,并且不再能够重试. 将其设为空以永不过期作业. 它必须不少于 1 天,例如: `15 days` , `1 month` , `2 years` . |
| `asset_proxy_enabled` | boolean | no | ( **如果启用,则要求:** `asset_proxy_url` )启用资产代理. 需要重启 GitLab 才能应用更改. |
| `asset_proxy_secret_key` | string | no | 与资产代理服务器共享的机密. 需要重启 GitLab 才能应用更改. |
| `asset_proxy_url` | string | no | 资产代理服务器的 URL. 需要重启 GitLab 才能应用更改. |
| `asset_proxy_whitelist` | 字符串或字符串数组 | no | 与这些域匹配的资产将不会被代理. 允许使用通配符. 您的 GitLab 安装网址会自动列入白名单. 需要重启 GitLab 才能应用更改. |
| `authorized_keys_enabled` | boolean | no | 默认情况下,我们无需经过其他配置即可写入`authorized_keys`文件以通过 SSH 支持 Git. 可以对 GitLab 进行优化,以通过数据库文件对 SSH 密钥进行身份验证. 仅当您已将 OpenSSH 服务器配置为使用 AuthorizedKeysCommand 时,才禁用此功能. |
| `auto_devops_domain` | string | no | 指定默认情况下用于每个项目的 Auto Review Apps 和 Auto Deploy 阶段的域. |
| `auto_devops_enabled` | boolean | no | 默认情况下,为项目启用 Auto DevOps. 它将基于预定义的 CI / CD 配置自动构建,测试和部署应用程序. |
| `check_namespace_plan` | boolean | no | 如果项目名称空间的计划包括该功能或项目为公共项目,则启用此选项将仅使许可的 EE 功能可用于项目. |
| `commit_email_hostname` | string | no | 自定义主机名(用于私人提交电子邮件). |
| `container_registry_token_expire_delay` | integer | no | 容器注册表令牌持续时间(以分钟为单位). |
| `default_artifacts_expire_in` | string | no | 设置每个作业的工件的默认到期时间. |
| `default_branch_protection` | integer | no | 确定开发者是否可以掌握. 可以采用: `0` *(不受保护,开发人员和维护人员都可以推送新的提交,强制推送或删除分支)* , `1` *(部分受保护的开发人员和维护人员可以推送新的提交,但是不能强制推送或删除分支)*或`2` *(受完全保护的开发人员无法推送新的提交,但维护者可以;没有人可以强制推送或删除分支)*作为参数. 默认值为`2` . |
| `default_ci_config_path` | string | no | 新项目的默认 CI 配置路径(如果未设置, `.gitlab-ci.yml` ). |
| `default_group_visibility` | string | no | 新群组获得的可见度级别. 可以将`private` , `internal`和`public`作为参数. 默认值为`private` . |
| `default_project_creation` | integer | no | 默认的项目创建保护. 可以采用: `0` *(无人)* , `1` *(维护者)*或`2` *(开发人员+维护者)* |
| `default_projects_limit` | integer | no | 每个用户的项目限制. 默认值为`100000` . |
| `default_project_visibility` | string | no | 新项目获得什么可见度级别. 可以将`private` , `internal`和`public`作为参数. 默认值为`private` . |
| `default_snippet_visibility` | string | no | 新摘要的可见性级别是多少. 可以将`private` , `internal`和`public`作为参数. 默认值为`private` . |
| `diff_max_patch_bytes` | integer | no | 最大差异补丁大小(字节). |
| `disabled_oauth_sign_in_sources` | 字符串数组 | no | 禁用的 OAuth 登录源. |
| `dns_rebinding_protection_enabled` | boolean | no | 实施 DNS 重新绑定攻击保护. |
| `domain_blacklist` | 字符串数组 | no | 电子邮件地址与这些域匹配的用户将无法注册. 允许使用通配符. 对多个条目使用单独的行. 例如: `domain.com` , `*.domain.com` . |
| `domain_blacklist_enabled` | boolean | no | ( **如果启用,则要求:** `domain_blacklist` )允许阻止来自特定域的电子邮件的注册. |
| `domain_whitelist` | 字符串数组 | no | 强迫人们仅使用公司电子邮件进行注册. 默认值为`null` ,表示没有限制. |
| `dsa_key_restriction` | integer | no | 上载 DSA 密钥的最小允许位长. 默认值为`0` (无限制). `-1`禁用 DSA 密钥. |
| `ecdsa_key_restriction` | integer | no | 上载的 ECDSA 密钥的最小允许曲线大小(以位为单位). 默认值为`0` (无限制). `-1`禁用 ECDSA 密钥. |
| `ed25519_key_restriction` | integer | no | 上载的 ED25519 密钥的最小允许曲线大小(以位为单位). 默认值为`0` (无限制). `-1`禁用 ED25519 键. |
| `eks_integration_enabled` | boolean | no | 启用与 Amazon EKS 的集成 |
| `eks_account_id` | string | no | 亚马逊帐号 |
| `eks_access_key_id` | string | no | AWS IAM 访问密钥 ID |
| `eks_secret_access_key` | string | no | AWS IAM 秘密访问密钥 |
| `elasticsearch_aws_access_key` | string | no | AWS IAM 访问密钥 |
| `elasticsearch_aws` | boolean | no | 启用使用 AWS 托管的 Elasticsearch |
| `elasticsearch_aws_region` | string | no | 配置 Elasticsearch 域的 AWS 区域 |
| `elasticsearch_aws_secret_access_key` | string | no | AWS IAM 秘密访问密钥 |
| `elasticsearch_indexed_field_length_limit` | integer | no | Elasticsearch 将索引的文本字段的最大大小. 0 值表示没有限制. 这不适用于存储库和 Wiki 索引. |
| `elasticsearch_indexing` | boolean | no | 启用 Elasticsearch 索引 |
| `elasticsearch_limit_indexing` | boolean | no | 限制 Elasticsearch 索引某些命名空间和项目 |
| `elasticsearch_max_bulk_concurrency` | integer | no | 每个索引操作的 Elasticsearch 批量请求的最大并发性. 这仅适用于存储库索引操作. |
| `elasticsearch_max_bulk_size_mb` | integer | no | Maximum size of Elasticsearch bulk indexing requests in MB. This only applies to repository indexing operations. |
| `elasticsearch_namespace_ids` | 整数数组 | no | 如果启用 elasticsearch_limit_indexing, `elasticsearch_limit_indexing`通过 Elasticsearch 进行索引的名称空间. |
| `elasticsearch_project_ids` | 整数数组 | no | 如果启用了 elasticsearch_limit_indexing, `elasticsearch_limit_indexing`通过 Elasticsearch 进行索引的项目. |
| `elasticsearch_search` | boolean | no | 启用 Elasticsearch 搜索 |
| `elasticsearch_url` | string | no | 用于连接到 Elasticsearch 的 URL. 使用逗号分隔的列表来支持集群(例如, `http://localhost:9200, http://localhost:9201"` ).如果您的 Elasticsearch 实例受密码保护,请在 URL 中传递`username:password` (例如, `http://<username>:<password>@<elastic_host>:9200/` ). |
| `email_additional_text` | string | no | 出于法律/审核/合规原因,在每封电子邮件的底部添加了其他文本 |
| `email_author_in_body` | boolean | no | 某些电子邮件服务器不支持覆盖电子邮件发件人名称. 启用此选项可在邮件正文中包含问题作者的名称,合并请求或评论. |
| `enabled_git_access_protocol` | string | no | 已启用 Git 访问协议. 允许的值为: `ssh` , `http`和`nil`以允许两种协议. |
| `enforce_terms` | boolean | no | ( **如果启用,则要求:** `terms` )对所有用户强制应用 ToS. |
| `external_auth_client_cert` | string | no | ( **如果启用,则要求:** `external_auth_client_key` )用于与外部授权服务进行身份验证的证书 |
| `external_auth_client_key_pass` | string | no | 与外部服务进行身份验证时用于私钥的密码,存储时会加密 |
| `external_auth_client_key` | string | 要求: `external_auth_client_cert` | 外部授权服务需要身份验证时证书的私钥,存储时将被加密 |
| `external_authorization_service_default_label` | string | 所需者: `external_authorization_service_enabled` | 请求授权时使用的默认分类标签,并且在项目上未指定任何分类标签 |
| `external_authorization_service_enabled` | boolean | no | ( **如果启用,则要求:** `external_authorization_service_default_label` , `external_authorization_service_timeout`和`external_authorization_service_url` )启用使用外部授权服务访问项目 |
| `external_authorization_service_timeout` | float | 所需者: `external_authorization_service_enabled` | 授权请求终止后的超时时间(以秒为单位). 当请求超时时,将拒绝用户访问. (最小值:0.001,最大值:10,步长:0.001) |
| `external_authorization_service_url` | string | 所需者: `external_authorization_service_enabled` | 授权请求将定向到的 URL |
| `file_template_project_id` | integer | no | 从中加载自定义文件模板的项目的 ID |
| `first_day_of_week` | integer | no | 日历视图和日期选择器的星期几开始. 有效值为星期日( `0` (默认),星期一( `1` )和星期六( `6` . |
| `geo_node_allowed_ips` | string | yes | 允许的辅助节点的 IP 和 CIDR 的逗号分隔列表. 例如`1.1.1.1, 2.2.2.0/24` . |
| `geo_status_timeout` | integer | no | 请求获取辅助节点状态的超时时间(秒). |
| `gitaly_timeout_default` | integer | no | 默认 Gitaly 超时(以秒为单位). 对于 Git 提取/推送操作或 Sidekiq 作业,不会强制使用此超时. 设置为`0`以禁用超时. |
| `gitaly_timeout_fast` | integer | no | 快速运行超时,以秒为单位. 预计某些 Gitaly 行动会很快. 如果它们超过此阈值,则存储碎片可能存在问题,并且"快速失败"可以帮助维护 GitLab 实例的稳定性. 设置为`0`以禁用超时. |
| `gitaly_timeout_medium` | integer | no | Gitaly 中度超时,以秒为单位. 这应该是快速超时和默认超时之间的一个值. 设置为`0`以禁用超时. |
| `grafana_enabled` | boolean | no | 启用 Grafana. |
| `grafana_url` | string | no | Grafana URL. |
| `gravatar_enabled` | boolean | no | 启用 Gravatar. |
| `hashed_storage_enabled` | boolean | no | 使用哈希存储路径创建新项目:启用基于哈希的不可变路径和存储库名称,以将存储库存储在磁盘上. 这样可以避免在项目 URL 更改时必须移动或重命名存储库,并可以提高磁盘 I / O 性能. (从 13.0 开始始终启用,在 14.0 中将删除配置) |
| `help_page_hide_commercial_content` | boolean | no | 隐藏帮助中与营销相关的条目. |
| `help_page_support_url` | string | no | 帮助页面和帮助下拉列表的备用支持 URL. |
| `help_page_text` | string | no | 帮助页面上显示的自定义文本. |
| `help_text` | string | no | GitLab 服务器管理员信息 |
| `hide_third_party_offers` | boolean | no | 不要在 GitLab 中显示来自第三方的报价. |
| `home_page_url` | string | no | 未登录时重定向到该 URL. |
| `housekeeping_bitmaps_enabled` | boolean | 要求: `housekeeping_enabled` | 启用 Git 包文件位图创建. |
| `housekeeping_enabled` | boolean | no | ( **如果启用,则要求:** `housekeeping_bitmaps_enabled` , `housekeeping_full_repack_period` , `housekeeping_gc_period`和`housekeeping_incremental_repack_period` ).启用或禁用 Git 整理. |
| `housekeeping_full_repack_period` | integer | 要求: `housekeeping_enabled` | Git 推送的次数,之后运行增量`git repack` . |
| `housekeeping_gc_period` | integer | 要求: `housekeeping_enabled` | 运行`git gc`之后的 Git 推送次数. |
| `housekeeping_incremental_repack_period` | integer | 要求: `housekeeping_enabled` | Git 推送的次数,之后运行增量`git repack` . |
| `html_emails_enabled` | boolean | no | 启用 HTML 电子邮件. |
| `import_sources` | 字符串数组 | no | 允许从中导入项目的来源,可能的值包括: `github` , `bitbucket` , `bitbucket_server` , `gitlab` , `google_code` , `fogbugz` , `git` , `gitlab_project` , `gitea` , `manifest`和`phabricator` . |
| `instance_statistics_visibility_private` | boolean | no | 设置为`true`实例统计信息仅对管理员可用. |
| `local_markdown_version` | integer | no | 当任何缓存的 Markdown 无效时,请增加此值. |
| `max_artifacts_size` | integer | no | 最大工件大小(MB) |
| `max_attachment_size` | integer | no | 限制附件大小(MB) |
| `max_import_size` | integer | no | 最大导入大小(MB). 0 代表无限. 默认值= 50 |
| `max_pages_size` | integer | no | 页面存储库的最大大小(MB) |
| `max_personal_access_token_lifetime` | integer | no | 个人访问令牌的最大允许寿命(天) |
| `metrics_method_call_threshold` | integer | no | 仅当方法调用花费的时间超过给定的毫秒数时,才会跟踪该方法调用. |
| `mirror_available` | boolean | no | 允许存储库镜像由项目维护者配置. 如果禁用,则只有管理员可以配置存储库镜像. |
| `mirror_capacity_threshold` | integer | no | 抢先计划更多镜像之前需要提供的最小容量 |
| `mirror_max_capacity` | integer | no | 可以同时同步的最大镜像数. |
| `mirror_max_delay` | integer | no | 计划进行同步时,镜像可以具有的两次更新之间的最长时间(以分钟为单位). |
| `npm_package_requests_forwarding` | boolean | no | 在 GitLab NPM 注册表中找不到软件包时,请使用 npmjs.org 作为默认的远程存储库 |
| `maintenance_mode` | boolean | no | 实例处于维护模式时,非管理员用户可以使用只读访问权限登录并发出只读 API 请求 |
| `maintenance_mode_message` | string | no | 实例处于维护模式时显示的消息 |
| `outbound_local_requests_whitelist` | 字符串数组 | no | 定义在禁用对钩子和服务的本地请求时允许对本地请求的信任域或 ip 地址的列表. |
| `pages_domain_verification_enabled` | boolean | no | 要求用户证明自定义域的所有权. 域验证是公共 GitLab 站点必不可少的安全措施. 在启用域之前,要求用户证明他们控制着域. |
| `password_authentication_enabled_for_git` | boolean | no | 通过 GitLab 帐户密码启用基于 HTTP(S)的 Git 身份验证. 默认值为`true` . |
| `password_authentication_enabled_for_web` | boolean | no | 通过 GitLab 帐户密码启用 Web 界面的身份验证. 默认值为`true` . |
| `performance_bar_allowed_group_id` | string | no | (不建议使用:改用`performance_bar_allowed_group_path` )允许切换性能栏的组的路径. |
| `performance_bar_allowed_group_path` | string | no | Path of the group that is allowed to toggle the performance bar. |
| `performance_bar_enabled` | boolean | no | (不建议使用:传递`performance_bar_allowed_group_path: nil`代替)允许启用性能栏. |
| `plantuml_enabled` | boolean | no | ( **如果启用,则要求:** `plantuml_url` )启用 PlantUML 集成. 默认值为`false` . |
| `plantuml_url` | string | 要求: `plantuml_enabled` | 用于集成的 PlantUML 实例 URL. |
| `polling_interval_multiplier` | decimal | no | Interval multiplier used by endpoints that perform polling. Set to `0` to disable polling. |
| `deletion_adjourned_period` | integer | no | 删除标记为删除的项目或组之前要等待的天数. 值必须介于 0 到 90 之间. |
| `project_export_enabled` | boolean | no | 启用项目导出. |
| `prometheus_metrics_enabled` | boolean | no | 启用 Prometheus 指标. |
| `protected_ci_variables` | boolean | no | 默认情况下,环境变量受保护. |
| `pseudonymizer_enabled` | boolean | no | 启用后,GitLab 将运行一个后台作业,该作业将生成 GitLab 数据库的假名化 CSV,并将其上传到您配置的对象存储目录中. |
| `push_event_hooks_limit` | integer | no | 一次按下更改(分支或标签)的次数,以确定是否将触发 Webhook 和服务. 如果超过该值,则不会提交 Webhooks 和服务. |
| `push_event_activities_limit` | integer | no | 一次推送中更改(分支或标签)的数量,以确定将创建单个推送事件还是批量推送事件. [如果批量推送事件](../user/admin_area/settings/push_event_activities_limit.html)超过该值, [则会创建](../user/admin_area/settings/push_event_activities_limit.html)该[事件](../user/admin_area/settings/push_event_activities_limit.html) . |
| `recaptcha_enabled` | boolean | no | ( **如果启用,则要求:** `recaptcha_private_key`和`recaptcha_site_key` )启用 reCAPTCHA. |
| `recaptcha_private_key` | string | 要求: `recaptcha_enabled` | reCAPTCHA 的私钥. |
| `recaptcha_site_key` | string | 要求: `recaptcha_enabled` | reCAPTCHA 的站点密钥. |
| `receive_max_input_size` | integer | no | 最大推送大小(MB). |
| `repository_checks_enabled` | boolean | no | GitLab 将在所有项目和 Wiki 存储库中定期运行`git fsck` ,以查找静默磁盘损坏问题. |
| `repository_size_limit` | integer | no | 每个存储库的大小限制(MB) |
| `repository_storages` | 字符串数组 | no | (GitLab 13.0 和更早版本)已启用的存储路径的名称列表,取自`gitlab.yml` . 在这些商店之一中创建新项目,这些项目是随机选择的. |
| `repository_storages_weighted` | 字符串哈希到整数 | no | (GitLab 13.1 和更高版本)从`gitlab.yml`到权重的名称的哈希值. 在这些存储库之一中创建新项目,并通过加权随机选择进行选择. |
| `require_two_factor_authentication` | boolean | no | ( **如果启用,则要求:** `two_factor_grace_period` )要求所有用户设置两因素身份验证. |
| `restricted_visibility_levels` | 字符串数组 | no | 非管理员用户不能将所选级别用于组,项目或摘要. 可以将`private` , `internal`和`public`作为参数. 默认值为`null` ,表示没有限制. |
| `rsa_key_restriction` | integer | no | 上载 RSA 密钥的最小允许比特长度. 默认值为`0` (无限制). `-1`禁用 RSA 密钥. |
| `send_user_confirmation_email` | boolean | no | 在注册时发送确认电子邮件. |
| `session_expire_delay` | integer | no | 会话持续时间(以分钟为单位). 需要重启 GitLab 才能应用更改 |
| `shared_runners_enabled` | boolean | no | ( **如果启用,则要求:** `shared_runners_text`和`shared_runners_minutes` )为新项目启用共享运行器. |
| `shared_runners_minutes` | integer | 所需者: `shared_runners_enabled` | 设置组每月可以在共享运行者上使用的最大管道分钟数. |
| `shared_runners_text` | string | 所需者: `shared_runners_enabled` | 共享跑步者文字. |
| `signin_enabled` | string | no | (不建议使用:改为使用`password_authentication_enabled_for_web` )该标志指示是否为 Web 界面启用了密码认证. |
| `sign_in_text` | string | no | 登录页面上的文本. |
| `signup_enabled` | boolean | no | 启用注册. 默认值为`true` . |
| `slack_app_enabled` | boolean | no | ( **如果启用,则要求:** `slack_app_id` , `slack_app_secret`和`slack_app_secret` )启用 Slack 应用. |
| `slack_app_id` | string | 所需者: `slack_app_enabled` | The app ID of the Slack-app. |
| `slack_app_secret` | string | 所需者: `slack_app_enabled` | Slack-app 的应用程序秘诀. |
| `slack_app_verification_token` | string | 所需者: `slack_app_enabled` | Slack-app 的验证令牌. |
| `snowplow_collector_hostname` | string | 所需者: `snowplow_enabled` | 扫雪机收集器主机名. (例如, `snowplow.trx.gitlab.net` ) |
| `snowplow_cookie_domain` | string | no | Snowplow cookie 域. (例如, `.gitlab.com` ) |
| `snowplow_enabled` | boolean | no | 启用扫雪机跟踪. |
| `snowplow_app_id` | string | no | Snowplow 站点名称/应用程序 ID. (例如`gitlab` ) |
| `snowplow_iglu_registry_url` | string | no | Snowplow 基本 Iglu Schema 注册表 URL,用于自定义上下文和自我描述事件' |
| `sourcegraph_enabled` | boolean | no | 启用 Sourcegraph 集成. 默认值为`false` . **如果启用,则需要** `sourcegraph_url` . |
| `sourcegraph_url` | string | 要求: `sourcegraph_enabled` | 用于集成的 Sourcegraph 实例 URL. |
| `sourcegraph_public_only` | boolean | no | 阻止将 Sourcegraph 加载到私有和内部项目中. 默认值为`true` . |
| `spam_check_endpoint_enabled` | boolean | no | 通过外部 API 端点启用垃圾邮件检查. 默认值为`false` . |
| `spam_check_endpoint_url` | string | no | 外部垃圾邮件检查服务端点的 URL. |
| `terminal_max_session_time` | integer | no | Web 终端 websocket 连接的最长时间(以秒为单位). 设置为`0`表示无限时间. |
| `terms` | text | 要求: `enforce_terms` | ( **要求:** `enforce_terms` )ToS 的降价内容. |
| `throttle_authenticated_api_enabled` | boolean | no | ( **如果启用,则要求:** `throttle_authenticated_api_period_in_seconds`和`throttle_authenticated_api_requests_per_period` )启用经过身份验证的 API 请求速率限制. 帮助减少请求量(例如,来自爬虫或恶意机器人的请求量). |
| `throttle_authenticated_api_period_in_seconds` | integer | 所需者: `throttle_authenticated_api_enabled` _ 已验证`throttle_authenticated_api_enabled` | 限速时间(秒). |
| `throttle_authenticated_api_requests_per_period` | integer | 所需者: `throttle_authenticated_api_enabled` _ 已验证`throttle_authenticated_api_enabled` | 每个用户每个时段的最大请求数. |
| `throttle_authenticated_web_enabled` | boolean | no | ( **如果启用,则要求:** `throttle_authenticated_web_period_in_seconds`和`throttle_authenticated_web_requests_per_period` )启用经过身份验证的 Web 请求速率限制. 帮助减少请求量(例如,来自爬虫或恶意机器人的请求量). |
| `throttle_authenticated_web_period_in_seconds` | integer | 所需者: `throttle_authenticated_web_enabled` _ 已验证网络 _ 已`throttle_authenticated_web_enabled` | 限速时间(秒). |
| `throttle_authenticated_web_requests_per_period` | integer | 所需者: `throttle_authenticated_web_enabled` _ 已验证网络 _ 已`throttle_authenticated_web_enabled` | 每个用户每个时段的最大请求数. |
| `throttle_unauthenticated_enabled` | boolean | no | ( **如果启用,则要求:** `throttle_unauthenticated_period_in_seconds`和`throttle_unauthenticated_requests_per_period` )启用未认证的请求速率限制. 帮助减少请求量(例如,来自爬虫或恶意机器人的请求量). |
| `throttle_unauthenticated_period_in_seconds` | integer | 所需者: `throttle_unauthenticated_enabled` _ 未`throttle_unauthenticated_enabled`的 _ `throttle_unauthenticated_enabled` | 限速时间(秒). |
| `throttle_unauthenticated_requests_per_period` | integer | required by: `throttle_unauthenticated_enabled` | 每个 IP 的每个周期的最大请求数. |
| `time_tracking_limit_to_hours` | boolean | no | 将时间跟踪单位的显示限制为小时. 默认值为`false` . |
| `two_factor_grace_period` | integer | 要求者: `require_two_factor_authentication` | 允许用户跳过两因素身份验证的强制配置的时间(以小时为单位). |
| `unique_ips_limit_enabled` | boolean | no | ( **如果启用,则要求:** `unique_ips_limit_per_user`和`unique_ips_limit_time_window` )限制从多个`unique_ips_limit_time_window`登录. |
| `unique_ips_limit_per_user` | integer | 所需者: `unique_ips_limit_enabled` | 每个用户的最大 IP 数. |
| `unique_ips_limit_time_window` | integer | 所需者: `unique_ips_limit_enabled` | IP 将计入限制多少秒. |
| `usage_ping_enabled` | boolean | no | GitLab 每周都会向 GitLab,Inc.报告许可证使用情况. |
| `user_default_external` | boolean | no | 默认情况下,新注册的用户将是外部用户. |
| `user_default_internal_regex` | string | no | 指定电子邮件地址正则表达式模式以标识默认的内部用户. |
| `user_oauth_applications` | boolean | no | 允许用户注册任何应用程序以将 GitLab 用作 OAuth 提供程序. |
| `user_show_add_ssh_key_message` | boolean | no | 设置为`false`时,向没有上载 SSH 密钥的用户显示"您将无法通过 SSH 推送或推送项目代码"警告. |
| `version_check_enabled` | boolean | no | 让 GitLab 在更新可用时通知您. |
| `web_ide_clientside_preview_enabled` | boolean | no | 实时预览(允许使用 CodeSandbox 实时预览在 Web IDE 中对 JavaScript 项目进行实时预览). |
| `snippet_size_limit` | integer | no | 摘录内容的最大大小(以**字节为单位)** . 默认值:52428800 字节(50MB). |
| `issues_create_limit` | integer | no | 每位用户每分钟每分钟最多可创建问题的请求数. 默认值:300.要禁用限制,请将其设置为 0. |
| `raw_blob_request_limit` | integer | no | 每条原始路径每分钟的最大请求数. 默认值:300.要禁用限制,请将其设置为 0. |
| `wiki_page_max_content_bytes` | integer | no | Wiki 页面的最大内容大小(以**字节为单位)** . 默认值:52428800 字节(50MB). |
- GitLab Docs
- Installation
- Requirements
- GitLab cloud native Helm Chart
- Install GitLab with Docker
- Installation from source
- Install GitLab on Microsoft Azure
- Installing GitLab on Google Cloud Platform
- Installing GitLab on Amazon Web Services (AWS)
- Analytics
- Code Review Analytics
- Productivity Analytics
- Value Stream Analytics
- Kubernetes clusters
- Adding and removing Kubernetes clusters
- Adding EKS clusters
- Adding GKE clusters
- Group-level Kubernetes clusters
- Instance-level Kubernetes clusters
- Canary Deployments
- Cluster Environments
- Deploy Boards
- GitLab Managed Apps
- Crossplane configuration
- Cluster management project (alpha)
- Kubernetes Logs
- Runbooks
- Serverless
- Deploying AWS Lambda function using GitLab CI/CD
- Securing your deployed applications
- Groups
- Contribution Analytics
- Custom group-level project templates
- Epics
- Manage epics
- Group Import/Export
- Insights
- Issues Analytics
- Iterations
- Public access
- SAML SSO for GitLab.com groups
- SCIM provisioning using SAML SSO for GitLab.com groups
- Subgroups
- Roadmap
- Projects
- GitLab Secure
- Security Configuration
- Container Scanning
- Dependency Scanning
- Dependency List
- Static Application Security Testing (SAST)
- Secret Detection
- Dynamic Application Security Testing (DAST)
- GitLab Security Dashboard
- Offline environments
- Standalone Vulnerability pages
- Security scanner integration
- Badges
- Bulk editing issues and merge requests at the project level
- Code Owners
- Compliance
- License Compliance
- Compliance Dashboard
- Create a project
- Description templates
- Deploy Keys
- Deploy Tokens
- File finder
- Project integrations
- Integrations
- Atlassian Bamboo CI Service
- Bugzilla Service
- Custom Issue Tracker service
- Discord Notifications service
- Enabling emails on push
- GitHub project integration
- Hangouts Chat service
- Atlassian HipChat
- Irker IRC Gateway
- GitLab Jira integration
- Mattermost Notifications Service
- Mattermost slash commands
- Microsoft Teams service
- Mock CI Service
- Prometheus integration
- Redmine Service
- Slack Notifications Service
- Slack slash commands
- GitLab Slack application
- Webhooks
- YouTrack Service
- Insights
- Issues
- Crosslinking Issues
- Design Management
- Confidential issues
- Due dates
- Issue Boards
- Issue Data and Actions
- Labels
- Managing issues
- Milestones
- Multiple Assignees for Issues
- Related issues
- Service Desk
- Sorting and ordering issue lists
- Issue weight
- Associate a Zoom meeting with an issue
- Merge requests
- Allow collaboration on merge requests across forks
- Merge Request Approvals
- Browser Performance Testing
- How to create a merge request
- Cherry-pick changes
- Code Quality
- Load Performance Testing
- Merge Request dependencies
- Fast-forward merge requests
- Merge when pipeline succeeds
- Merge request conflict resolution
- Reverting changes
- Reviewing and managing merge requests
- Squash and merge
- Merge requests versions
- Draft merge requests
- Members of a project
- Migrating projects to a GitLab instance
- Import your project from Bitbucket Cloud to GitLab
- Import your project from Bitbucket Server to GitLab
- Migrating from ClearCase
- Migrating from CVS
- Import your project from FogBugz to GitLab
- Gemnasium
- Import your project from GitHub to GitLab
- Project importing from GitLab.com to your private GitLab instance
- Import your project from Gitea to GitLab
- Import your Jira project issues to GitLab
- Migrating from Perforce Helix
- Import Phabricator tasks into a GitLab project
- Import multiple repositories by uploading a manifest file
- Import project from repo by URL
- Migrating from SVN to GitLab
- Migrating from TFVC to Git
- Push Options
- Releases
- Repository
- Branches
- Git Attributes
- File Locking
- Git file blame
- Git file history
- Repository mirroring
- Protected branches
- Protected tags
- Push Rules
- Reduce repository size
- Signing commits with GPG
- Syntax Highlighting
- GitLab Web Editor
- Web IDE
- Requirements Management
- Project settings
- Project import/export
- Project access tokens (Alpha)
- Share Projects with other Groups
- Snippets
- Static Site Editor
- Wiki
- Project operations
- Monitor metrics for your CI/CD environment
- Set up alerts for Prometheus metrics
- Embedding metric charts within GitLab-flavored Markdown
- Embedding Grafana charts
- Using the Metrics Dashboard
- Dashboard YAML properties
- Metrics dashboard settings
- Panel types for dashboards
- Using Variables
- Templating variables for metrics dashboards
- Prometheus Metrics library
- Monitoring AWS Resources
- Monitoring HAProxy
- Monitoring Kubernetes
- Monitoring NGINX
- Monitoring NGINX Ingress Controller
- Monitoring NGINX Ingress Controller with VTS metrics
- Alert Management
- Error Tracking
- Tracing
- Incident Management
- GitLab Status Page
- Feature Flags
- GitLab CI/CD
- GitLab CI/CD pipeline configuration reference
- GitLab CI/CD include examples
- Introduction to CI/CD with GitLab
- Getting started with GitLab CI/CD
- How to enable or disable GitLab CI/CD
- Using SSH keys with GitLab CI/CD
- Migrating from CircleCI
- Migrating from Jenkins
- Auto DevOps
- Getting started with Auto DevOps
- Requirements for Auto DevOps
- Customizing Auto DevOps
- Stages of Auto DevOps
- Upgrading PostgreSQL for Auto DevOps
- Cache dependencies in GitLab CI/CD
- GitLab ChatOps
- Cloud deployment
- Docker integration
- Building Docker images with GitLab CI/CD
- Using Docker images
- Building images with kaniko and GitLab CI/CD
- GitLab CI/CD environment variables
- Predefined environment variables reference
- Where variables can be used
- Deprecated GitLab CI/CD variables
- Environments and deployments
- Protected Environments
- GitLab CI/CD Examples
- Test a Clojure application with GitLab CI/CD
- Using Dpl as deployment tool
- Testing a Phoenix application with GitLab CI/CD
- End-to-end testing with GitLab CI/CD and WebdriverIO
- DevOps and Game Dev with GitLab CI/CD
- Deploy a Spring Boot application to Cloud Foundry with GitLab CI/CD
- How to deploy Maven projects to Artifactory with GitLab CI/CD
- Testing PHP projects
- Running Composer and NPM scripts with deployment via SCP in GitLab CI/CD
- Test and deploy Laravel applications with GitLab CI/CD and Envoy
- Test and deploy a Python application with GitLab CI/CD
- Test and deploy a Ruby application with GitLab CI/CD
- Test and deploy a Scala application to Heroku
- GitLab CI/CD for external repositories
- Using GitLab CI/CD with a Bitbucket Cloud repository
- Using GitLab CI/CD with a GitHub repository
- GitLab Pages
- GitLab Pages
- GitLab Pages domain names, URLs, and baseurls
- Create a GitLab Pages website from scratch
- Custom domains and SSL/TLS Certificates
- GitLab Pages integration with Let's Encrypt
- GitLab Pages Access Control
- Exploring GitLab Pages
- Incremental Rollouts with GitLab CI/CD
- Interactive Web Terminals
- Optimizing GitLab for large repositories
- Metrics Reports
- CI/CD pipelines
- Pipeline Architecture
- Directed Acyclic Graph
- Multi-project pipelines
- Parent-child pipelines
- Pipelines for Merge Requests
- Pipelines for Merged Results
- Merge Trains
- Job artifacts
- Pipeline schedules
- Pipeline settings
- Triggering pipelines through the API
- Review Apps
- Configuring GitLab Runners
- GitLab CI services examples
- Using MySQL
- Using PostgreSQL
- Using Redis
- Troubleshooting CI/CD
- GitLab Package Registry
- GitLab Container Registry
- Dependency Proxy
- GitLab Composer Repository
- GitLab Conan Repository
- GitLab Maven Repository
- GitLab NPM Registry
- GitLab NuGet Repository
- GitLab PyPi Repository
- API Docs
- API resources
- .gitignore API
- GitLab CI YMLs API
- Group and project access requests API
- Appearance API
- Applications API
- Audit Events API
- Avatar API
- Award Emoji API
- Project badges API
- Group badges API
- Branches API
- Broadcast Messages API
- Project clusters API
- Group clusters API
- Instance clusters API
- Commits API
- Container Registry API
- Custom Attributes API
- Dashboard annotations API
- Dependencies API
- Deploy Keys API
- Deployments API
- Discussions API
- Dockerfiles API
- Environments API
- Epics API
- Events
- Feature Flags API
- Feature flag user lists API
- Freeze Periods API
- Geo Nodes API
- Group Activity Analytics API
- Groups API
- Import API
- Issue Boards API
- Group Issue Boards API
- Issues API
- Epic Issues API
- Issues Statistics API
- Jobs API
- Keys API
- Labels API
- Group Labels API
- License
- Licenses API
- Issue links API
- Epic Links API
- Managed Licenses API
- Markdown API
- Group and project members API
- Merge request approvals API
- Merge requests API
- Project milestones API
- Group milestones API
- Namespaces API
- Notes API
- Notification settings API
- Packages API
- Pages domains API
- Pipeline schedules API
- Pipeline triggers API
- Pipelines API
- Project Aliases API
- Project import/export API
- Project repository storage moves API
- Project statistics API
- Project templates API
- Projects API
- Protected branches API
- Protected tags API
- Releases API
- Release links API
- Repositories API
- Repository files API
- Repository submodules API
- Resource label events API
- Resource milestone events API
- Resource weight events API
- Runners API
- SCIM API
- Search API
- Services API
- Application settings API
- Sidekiq Metrics API
- Snippets API
- Project snippets
- Application statistics API
- Suggest Changes API
- System hooks API
- Tags API
- Todos API
- Users API
- Project-level Variables API
- Group-level Variables API
- Version API
- Vulnerabilities API
- Vulnerability Findings API
- Wikis API
- GraphQL API
- Getting started with GitLab GraphQL API
- GraphQL API Resources
- API V3 to API V4
- Validate the .gitlab-ci.yml (API)
- User Docs
- Abuse reports
- User account
- Active sessions
- Deleting a User account
- Permissions
- Personal access tokens
- Profile preferences
- Threads
- GitLab and SSH keys
- GitLab integrations
- Git
- GitLab.com settings
- Infrastructure as code with Terraform and GitLab
- GitLab keyboard shortcuts
- GitLab Markdown
- AsciiDoc
- GitLab Notification Emails
- GitLab Quick Actions
- Autocomplete characters
- Reserved project and group names
- Search through GitLab
- Advanced Global Search
- Advanced Syntax Search
- Time Tracking
- GitLab To-Do List
- Administrator Docs
- Reference architectures
- Reference architecture: up to 1,000 users
- Reference architecture: up to 2,000 users
- Reference architecture: up to 3,000 users
- Reference architecture: up to 5,000 users
- Reference architecture: up to 10,000 users
- Reference architecture: up to 25,000 users
- Reference architecture: up to 50,000 users
- Troubleshooting a reference architecture set up
- Working with the bundled Consul service
- Configuring PostgreSQL for scaling
- Configuring GitLab application (Rails)
- Load Balancer for multi-node GitLab
- Configuring a Monitoring node for Scaling and High Availability
- NFS
- Working with the bundled PgBouncer service
- Configuring Redis for scaling
- Configuring Sidekiq
- Admin Area settings
- Continuous Integration and Deployment Admin settings
- Custom instance-level project templates
- Diff limits administration
- Enable and disable GitLab features deployed behind feature flags
- Geo nodes Admin Area
- GitLab Pages administration
- Health Check
- Job logs
- Labels administration
- Log system
- PlantUML & GitLab
- Repository checks
- Repository storage paths
- Repository storage types
- Account and limit settings
- Service templates
- System hooks
- Changing your time zone
- Uploads administration
- Abuse reports
- Activating and deactivating users
- Audit Events
- Blocking and unblocking users
- Broadcast Messages
- Elasticsearch integration
- Gitaly
- Gitaly Cluster
- Gitaly reference
- Monitoring GitLab
- Monitoring GitLab with Prometheus
- Performance Bar
- Usage statistics
- Object Storage
- Performing Operations in GitLab
- Cleaning up stale Redis sessions
- Fast lookup of authorized SSH keys in the database
- Filesystem Performance Benchmarking
- Moving repositories managed by GitLab
- Run multiple Sidekiq processes
- Sidekiq MemoryKiller
- Switching to Puma
- Understanding Unicorn and unicorn-worker-killer
- User lookup via OpenSSH's AuthorizedPrincipalsCommand
- GitLab Package Registry administration
- GitLab Container Registry administration
- Replication (Geo)
- Geo database replication
- Geo with external PostgreSQL instances
- Geo configuration
- Using a Geo Server
- Updating the Geo nodes
- Geo with Object storage
- Docker Registry for a secondary node
- Geo for multiple nodes
- Geo security review (Q&A)
- Location-aware Git remote URL with AWS Route53
- Tuning Geo
- Removing secondary Geo nodes
- Geo data types support
- Geo Frequently Asked Questions
- Geo Troubleshooting
- Geo validation tests
- Disaster Recovery (Geo)
- Disaster recovery for planned failover
- Bring a demoted primary node back online
- Automatic background verification
- Rake tasks
- Back up and restore GitLab
- Clean up
- Namespaces
- Maintenance Rake tasks
- Geo Rake Tasks
- GitHub import
- Import bare repositories
- Integrity check Rake task
- LDAP Rake tasks
- Listing repository directories
- Praefect Rake tasks
- Project import/export administration
- Repository storage Rake tasks
- Generate sample Prometheus data
- Uploads migrate Rake tasks
- Uploads sanitize Rake tasks
- User management
- Webhooks administration
- X.509 signatures
- Server hooks
- Static objects external storage
- Updating GitLab
- GitLab release and maintenance policy
- Security
- Password Storage
- Custom password length limits
- Restrict allowed SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- How to reset your root password
- How to unlock a locked user from the command line
- User File Uploads
- How we manage the TLS protocol CRIME vulnerability
- User email confirmation at sign-up
- Security of running jobs
- Proxying assets
- CI/CD Environment Variables
- Contributor and Development Docs
- Contribute to GitLab
- Community members & roles
- Implement design & UI elements
- Issues workflow
- Merge requests workflow
- Code Review Guidelines
- Style guides
- GitLab Architecture Overview
- CI/CD development documentation
- Database guides
- Database Review Guidelines
- Database Review Guidelines
- Migration Style Guide
- What requires downtime?
- Understanding EXPLAIN plans
- Rake tasks for developers
- Mass inserting Rails models
- GitLab Documentation guidelines
- Documentation Style Guide
- Documentation structure and template
- Documentation process
- Documentation site architecture
- Global navigation
- GitLab Docs monthly release process
- Telemetry Guide
- Usage Ping Guide
- Snowplow Guide
- Experiment Guide
- Feature flags in development of GitLab
- Feature flags process
- Developing with feature flags
- Feature flag controls
- Document features deployed behind feature flags
- Frontend Development Guidelines
- Accessibility & Readability
- Ajax
- Architecture
- Axios
- Design Patterns
- Frontend Development Process
- DropLab
- Emojis
- Filter
- Frontend FAQ
- GraphQL
- Icons and SVG Illustrations
- InputSetter
- Performance
- Principles
- Security
- Tooling
- Vuex
- Vue
- Geo (development)
- Geo self-service framework (alpha)
- Gitaly developers guide
- GitLab development style guides
- API style guide
- Go standards and style guidelines
- GraphQL API style guide
- Guidelines for shell commands in the GitLab codebase
- HTML style guide
- JavaScript style guide
- Migration Style Guide
- Newlines style guide
- Python Development Guidelines
- SCSS style guide
- Shell scripting standards and style guidelines
- Sidekiq debugging
- Sidekiq Style Guide
- SQL Query Guidelines
- Vue.js style guide
- Instrumenting Ruby code
- Testing standards and style guidelines
- Flaky tests
- Frontend testing standards and style guidelines
- GitLab tests in the Continuous Integration (CI) context
- Review Apps
- Smoke Tests
- Testing best practices
- Testing levels
- Testing Rails migrations at GitLab
- Testing Rake tasks
- End-to-end Testing
- Beginner's guide to writing end-to-end tests
- End-to-end testing Best Practices
- Dynamic Element Validation
- Flows in GitLab QA
- Page objects in GitLab QA
- Resource class in GitLab QA
- Style guide for writing end-to-end tests
- Testing with feature flags
- Translate GitLab to your language
- Internationalization for GitLab
- Translating GitLab
- Proofread Translations
- Merging translations from CrowdIn
- Value Stream Analytics development guide
- GitLab subscription
- Activate GitLab EE with a license