From ca0ea54efa15ccaf2043e5eda4047eeec8875532 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Tue, 17 Jun 2025 21:11:08 +0000 Subject: [PATCH] Add latest changes from gitlab-org/gitlab@master --- doc/api/dependency_list_export.md | 1 + doc/api/project_templates.md | 21 +++++++ doc/api/rest/troubleshooting.md | 2 +- .../pipelines/mr_pipeline_troubleshooting.md | 2 +- .../eclipse/troubleshooting.md | 2 +- .../jetbrains_troubleshooting.md | 2 +- .../neovim/neovim_troubleshooting.md | 2 +- .../background_migrations_troubleshooting.md | 2 +- doc/update/package/package_troubleshooting.md | 2 +- .../api_fuzzing/troubleshooting.md | 2 +- .../api_security_testing/troubleshooting.md | 2 +- .../dast/browser/troubleshooting.md | 6 +- .../compliance_standards.md | 57 +++++++++++++++++++ doc/user/duo_workflow/_index.md | 2 +- doc/user/duo_workflow/troubleshooting.md | 2 +- doc/user/gitlab_duo_chat/agentic_chat.md | 2 +- doc/user/gitlab_duo_chat/troubleshooting.md | 2 +- .../merge_request_troubleshooting.md | 2 +- 18 files changed, 96 insertions(+), 17 deletions(-) diff --git a/doc/api/dependency_list_export.md b/doc/api/dependency_list_export.md index c6a0e4277ce..63c57ff9ad1 100644 --- a/doc/api/dependency_list_export.md +++ b/doc/api/dependency_list_export.md @@ -71,6 +71,7 @@ Exports can be requested in different file formats. Some formats are only availa | ----------- | ----------- | ------------- | | `dependency_list` | A standard JSON object that lists the dependencies as key-value pairs. | Projects | | `sbom` | A [CycloneDX](https://cyclonedx.org/) 1.4 bill of materials | Pipelines | +| `cyclonedx_1_6_json` | A [CycloneDX](https://cyclonedx.org/) 1.6 bill of materials | Projects | | `json_array` | A flat JSON array that contains component objects. | Groups | | `csv` | A comma-separated values (CSV) document. | Projects, Groups | diff --git a/doc/api/project_templates.md b/doc/api/project_templates.md index 1b783cdfca4..bdce5186e7b 100644 --- a/doc/api/project_templates.md +++ b/doc/api/project_templates.md @@ -38,6 +38,13 @@ GET /projects/:id/templates/:type | `id` | integer or string | Yes | The ID or [URL-encoded path of the project](rest/_index.md#namespaced-paths). | | `type` | string | Yes | The type of the template. Accepted values are: `dockerfiles`, `gitignores`, `gitlab_ci_ymls`, `licenses`, `issues`, or `merge_requests`. | +Example request: + +```shell +curl --header "PRIVATE-TOKEN: " \ + --url "https://gitlab.example.com/api/v4/projects/1/templates/licenses" +``` + Example response (licenses): ```json @@ -108,6 +115,13 @@ GET /projects/:id/templates/:type/:name | `project` | string | No | The project name to use when expanding placeholders in the template. Affects only licenses. | | `source_template_project_id` | integer | No | The project ID where a given template is being stored. Helpful when multiple templates from different projects have the same name. If multiple templates have the same name, the match from `closest ancestor` is returned if `source_template_project_id` is not specified, | +Example request: + +```shell +curl --header "PRIVATE-TOKEN: " \ + --url "https://gitlab.example.com/api/v4/projects/1/templates/dockerfiles/Binary" +``` + Example response (Dockerfile): ```json @@ -117,6 +131,13 @@ Example response (Dockerfile): } ``` +Example request: + +```shell +curl --header "PRIVATE-TOKEN: " \ + --url "https://gitlab.example.com/api/v4/projects/1/templates/licenses/mit" +``` + Example response (license): ```json diff --git a/doc/api/rest/troubleshooting.md b/doc/api/rest/troubleshooting.md index 53ac3c79f98..75c9455b34a 100644 --- a/doc/api/rest/troubleshooting.md +++ b/doc/api/rest/troubleshooting.md @@ -3,7 +3,7 @@ stage: Foundations group: Import and Integrate info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments description: Programmatic interaction with GitLab. -title: REST API troubleshooting +title: Troubleshooting the REST API --- {{< details >}} diff --git a/doc/ci/pipelines/mr_pipeline_troubleshooting.md b/doc/ci/pipelines/mr_pipeline_troubleshooting.md index 99f84db1d43..e7f2ee9a2dc 100644 --- a/doc/ci/pipelines/mr_pipeline_troubleshooting.md +++ b/doc/ci/pipelines/mr_pipeline_troubleshooting.md @@ -2,7 +2,7 @@ stage: Verify group: Pipeline Execution info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments -title: Merge request pipeline troubleshooting +title: Troubleshooting merge request pipelines --- {{< details >}} diff --git a/doc/editor_extensions/eclipse/troubleshooting.md b/doc/editor_extensions/eclipse/troubleshooting.md index c0acb7feec2..1aae9536b2e 100644 --- a/doc/editor_extensions/eclipse/troubleshooting.md +++ b/doc/editor_extensions/eclipse/troubleshooting.md @@ -3,7 +3,7 @@ stage: Create group: Editor Extensions info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments description: Connect and use GitLab Duo in Eclipse. -title: Eclipse troubleshooting +title: Troubleshooting Eclipse --- {{< details >}} diff --git a/doc/editor_extensions/jetbrains_ide/jetbrains_troubleshooting.md b/doc/editor_extensions/jetbrains_ide/jetbrains_troubleshooting.md index fd4722cb13a..8516e55c825 100644 --- a/doc/editor_extensions/jetbrains_ide/jetbrains_troubleshooting.md +++ b/doc/editor_extensions/jetbrains_ide/jetbrains_troubleshooting.md @@ -3,7 +3,7 @@ stage: Create group: Editor Extensions info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments description: Connect and use GitLab Duo in JetBrains IDEs. -title: JetBrains troubleshooting +title: Troubleshooting JetBrains --- If the steps on this page don't solve your problem, check the diff --git a/doc/editor_extensions/neovim/neovim_troubleshooting.md b/doc/editor_extensions/neovim/neovim_troubleshooting.md index 16f48b6621b..e053b13193f 100644 --- a/doc/editor_extensions/neovim/neovim_troubleshooting.md +++ b/doc/editor_extensions/neovim/neovim_troubleshooting.md @@ -3,7 +3,7 @@ stage: Create group: Editor Extensions info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments description: Connect and use GitLab Duo in Neovim. -title: Neovim troubleshooting +title: Troubleshooting Neovim --- When troubleshooting the GitLab plugin for Neovim, you should confirm if an issue still occurs diff --git a/doc/update/background_migrations_troubleshooting.md b/doc/update/background_migrations_troubleshooting.md index 56a6c2c5f28..183025c52e1 100644 --- a/doc/update/background_migrations_troubleshooting.md +++ b/doc/update/background_migrations_troubleshooting.md @@ -2,7 +2,7 @@ stage: Data Access group: Database Frameworks info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments -title: Troubleshooting +title: Troubleshooting background migrations --- {{< details >}} diff --git a/doc/update/package/package_troubleshooting.md b/doc/update/package/package_troubleshooting.md index 68eb820ae3f..69a35e77001 100644 --- a/doc/update/package/package_troubleshooting.md +++ b/doc/update/package/package_troubleshooting.md @@ -2,7 +2,7 @@ stage: GitLab Delivery group: Self Managed info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments -title: Troubleshooting +title: Troubleshooting package installation --- {{< details >}} diff --git a/doc/user/application_security/api_fuzzing/troubleshooting.md b/doc/user/application_security/api_fuzzing/troubleshooting.md index cea2d65423a..f8d4a1b3485 100644 --- a/doc/user/application_security/api_fuzzing/troubleshooting.md +++ b/doc/user/application_security/api_fuzzing/troubleshooting.md @@ -2,7 +2,7 @@ stage: Application Security Testing group: Dynamic Analysis info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments -title: Troubleshooting +title: Troubleshooting API Fuzzing jobs --- ## API Fuzzing job times out after N hours diff --git a/doc/user/application_security/api_security_testing/troubleshooting.md b/doc/user/application_security/api_security_testing/troubleshooting.md index 1ddc7ea06f0..06fd0749c73 100644 --- a/doc/user/application_security/api_security_testing/troubleshooting.md +++ b/doc/user/application_security/api_security_testing/troubleshooting.md @@ -2,7 +2,7 @@ stage: Application Security Testing group: Dynamic Analysis info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments -title: Troubleshooting +title: Troubleshooting API security testing jobs --- ## API security testing job times out after N hours diff --git a/doc/user/application_security/dast/browser/troubleshooting.md b/doc/user/application_security/dast/browser/troubleshooting.md index b1d58939087..4e0442b95ea 100644 --- a/doc/user/application_security/dast/browser/troubleshooting.md +++ b/doc/user/application_security/dast/browser/troubleshooting.md @@ -3,7 +3,7 @@ type: reference, howto stage: Application Security Testing group: Dynamic Analysis info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments -title: Troubleshooting +title: Troubleshooting DAST scans --- The following troubleshooting scenarios have been collected from customer support cases. If you @@ -167,7 +167,7 @@ The modules that can be configured for logging are as follows: As a simpler alternative to configuring log modules with `DAST_LOG_FILE_CONFIG`, you can set `SECURE_LOG_LEVEL`: -- To any of the [supported log levels](#log-levels). +- To any of the [supported log levels](#log-levels). When you do this, the specified level becomes the default log level in the log file for all modules. - To `debug` or `trace` to enable the [auth report](configuration/authentication.md#configure-the-authentication-report). - To `trace` to enable [DevTools logging](#chromium-devtools-logging). @@ -183,7 +183,7 @@ dast: SECURE_LOG_LEVEL: "trace" # is equivalent to: # DAST_LOG_FILE_CONFIG: "loglevel:trace" - # DAST_LOG_DEVTOOLS_CONFIG: "Default:messageAndBody,truncate:2000" + # DAST_LOG_DEVTOOLS_CONFIG: "Default:messageAndBody,truncate:2000" # DAST_AUTH_REPORT: "true" ``` diff --git a/doc/user/compliance/compliance_frameworks/compliance_standards.md b/doc/user/compliance/compliance_frameworks/compliance_standards.md index fedc363f85a..3bfd6ac444f 100644 --- a/doc/user/compliance/compliance_frameworks/compliance_standards.md +++ b/doc/user/compliance/compliance_frameworks/compliance_standards.md @@ -24,6 +24,63 @@ compliance standards. The [Compliance Adherence Templates](https://gitlab.com/gitlab-org/software-supply-chain-security/compliance/engineering/compliance-adherence-templates) project contains a library of JSON templates. Use these templates to quickly adopt predefined compliance frameworks. +## FedRAMP compliance requirements + +FedRAMP (Federal Risk and Authorization Management Program) categorizes cloud services into three impact levels: Low, Moderate, and High, based on the potential impact of a data breach on government operations, assets, or individuals. These levels correspond to different sets of security controls and requirements that cloud service providers (CSPs) must meet to achieve FedRAMP authorization. Controls are available for FedRAMP Low, FedRAMP Moderate, and FedRAMP High compliance. + +### FedRAMP Low compliance requirements + +The following table lists the requirements supported by GitLab for FedRAMP Low and the controls for the requirements. + +| FedRAMP Low requirement | Description | Supported controls | +|:-----------------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------| +| CM-5: Access Restrictions for Change | Define, document, approve, and enforce physical and logical access restrictions associated with changes to the system. |
  • Default branch protected
  • At least two approvals
| +| CM-6: Configuration Settings | Establish and document configuration settings for components employed in the system that reflect the most restrictive mode consistent with operational requirements using organization-defined common secure configurations; implement the configuration settings; identify, document, and approve any deviations from established configuration settings for organization-defined system components based on organization-defined operational requirements; and monitor and control changes to the configuration settings in accordance with organizational policies and procedures. |
  • Author approved merge request is forbidden
| +| CM-7: Least Functionality | Configure the system to provide only organization-defined mission essential capabilities; and prohibit or restrict organization-defined functions, system ports, protocols, software, or services. |
  • Committers approved merge request is forbidden
  • Merge requests approval rules prevent editing
| +| CM-10: Software Usage Restrictions | Use software and associated documentation in accordance with contract agreements and copyright laws; track the use of software and associated documentation protected by quantity licenses to control copying and distribution; and control and document the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work. |
  • License compliance running
| +| IA-2(12): Acceptance of PIV Credentials | Accept and electronically verify Personal Identity Verification (PIV) credentials. |
  • Auth SSO enabled
| +| IA-8(1): Acceptance of PIV Credentials From Other Agencies | Accept and electronically verify Personal Identity Verification (PIV) credentials from other federal agencies. |
  • Auth SSO enabled
| +| RA-5: Vulnerability Monitoring and Scanning | Scan for vulnerabilities in the system and hosted applications; employ vulnerability scanning tools and techniques; analyze vulnerability scan reports and results; remediate legitimate vulnerabilities; and share vulnerability information. |
  • Dependency scanning running
  • Container scanning running
  • DAST running
  • API security running
  • Fuzz testing running
| + +### FedRAMP Moderate compliance requirements + +The following table lists the requirements supported by GitLab for FedRAMP Moderate and the controls for the requirements. + +| FedRAMP Moderate requirement | Description | Supported controls | +|:-----------------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------| +| AC-5: Separation of Duties | Separate duties of individuals to prevent malevolent activity without collusion; document separation of duties; and define system access authorizations to support separation of duties. |
  • At least two approvals
  • Author approved merge request is forbidden
  • Committers approved merge request is forbidden
  • Merge requests approval rules prevent editing
| +| CM-3: Configuration Change Control | Determine and document the types of changes to the system that are configuration-controlled; review proposed configuration-controlled changes and approve or disapprove such changes with explicit consideration for security and privacy impact analyses; document configuration change decisions; implement approved configuration-controlled changes to the system; retain records of configuration-controlled changes to the system for organization-defined time period; monitor and review activities associated with configuration-controlled changes to the system; and coordinate and provide oversight for configuration change control activities through organization-defined configuration change control element. |
  • Default branch protected
  • At least two approvals
  • Author approved merge request is forbidden
  • Committers approved merge request is forbidden
  • Merge requests approval rules prevent editing
| +| CM-5: Access Restrictions for Change | Define, document, approve, and enforce physical and logical access restrictions associated with changes to the system. |
  • Default branch protected
  • At least two approvals
| +| CM-6: Configuration Settings | Establish and document configuration settings for components employed in the system that reflect the most restrictive mode consistent with operational requirements using organization-defined common secure configurations; implement the configuration settings; identify, document, and approve any deviations from established configuration settings for organization-defined system components based on organization-defined operational requirements; and monitor and control changes to the configuration settings in accordance with organizational policies and procedures. |
  • Author approved merge request is forbidden
| +| CM-7: Least Functionality | Configure the system to provide only organization-defined mission essential capabilities; and prohibit or restrict organization-defined functions, system ports, protocols, software, or services. |
  • Committers approved merge request is forbidden
  • Merge requests approval rules prevent editing
| +| CM-10: Software Usage Restrictions | Use software and associated documentation in accordance with contract agreements and copyright laws; track the use of software and associated documentation protected by quantity licenses to control copying and distribution; and control and document the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work. |
  • License compliance running
| +| IA-2(12): Acceptance of PIV Credentials | Accept and electronically verify Personal Identity Verification (PIV) credentials. |
  • Auth SSO enabled
| +| IA-5(7): No Embedded Unencrypted Static Authenticators | Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage. |
  • Secret detection running
| +| IA-8(1): Acceptance of PIV Credentials From Other Agencies | Accept and electronically verify Personal Identity Verification (PIV) credentials from other federal agencies. |
  • Auth SSO enabled
| +| RA-5: Vulnerability Monitoring and Scanning | Scan for vulnerabilities in the system and hosted applications; employ vulnerability scanning tools and techniques; analyze vulnerability scan reports and results; remediate legitimate vulnerabilities; and share vulnerability information. |
  • Dependency scanning running
  • Container scanning running
  • DAST running
  • API security running
  • Fuzz testing running
| +| SA-11(1): Static Code Analysis | Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of the analysis. |
  • SAST running
| +| SA-11(8): Dynamic Code Analysis | Require the developer of the system, system component, or system service to employ dynamic code analysis tools to identify common flaws and document the results of the analysis. |
  • DAST running
  • Fuzz testing running
| + +### FedRAMP High compliance requirements + +The following table lists the requirements supported by GitLab for FedRAMP High and the controls for the requirements. + +| FedRAMP High requirement | Description | Supported controls | +|:---------------------------------------------------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:-------------------| +| AC-5: Separation of Duties | Separate duties of individuals to prevent malevolent activity without collusion; document separation of duties; and define system access authorizations to support separation of duties. |
  • At least two approvals
  • Author approved merge request is forbidden
  • Committers approved merge request is forbidden
  • Merge requests approval rules prevent editing
| +| CM-3: Configuration Change Control | Determine and document the types of changes to the system that are configuration-controlled; review proposed configuration-controlled changes and approve or disapprove such changes with explicit consideration for security and privacy impact analyses; document configuration change decisions; implement approved configuration-controlled changes to the system; retain records of configuration-controlled changes to the system for organization-defined time period; monitor and review activities associated with configuration-controlled changes to the system; and coordinate and provide oversight for configuration change control activities through organization-defined configuration change control element. |
  • Default branch protected
  • At least two approvals
  • Author approved merge request is forbidden
  • Committers approved merge request is forbidden
  • Merge requests approval rules prevent editing
| +| CM-3(1): Automated Documentation, Notification, and Prohibition of Changes | Use automated mechanisms to document proposed changes to the system; notify organization-defined approval authorities; highlight change approvals that have not been received by organization-defined time period; prohibit changes to the system until designated approvals are received; and document all changes to the system. |
  • At least two approvals
  • Author approved merge request is forbidden
  • Committers approved merge request is forbidden
  • Merge requests approval rules prevent editing
| +| CM-5: Access Restrictions for Change | Define, document, approve, and enforce physical and logical access restrictions associated with changes to the system. |
  • Default branch protected
  • At least two approvals
| +| CM-6: Configuration Settings | Establish and document configuration settings for components employed in the system that reflect the most restrictive mode consistent with operational requirements using organization-defined common secure configurations; implement the configuration settings; identify, document, and approve any deviations from established configuration settings for organization-defined system components based on organization-defined operational requirements; and monitor and control changes to the configuration settings in accordance with organizational policies and procedures. |
  • Author approved merge request is forbidden
| +| CM-7: Least Functionality | Configure the system to provide only organization-defined mission essential capabilities; and prohibit or restrict organization-defined functions, system ports, protocols, software, or services. |
  • Committers approved merge request is forbidden
  • Merge requests approval rules prevent editing
| +| CM-10: Software Usage Restrictions | Use software and associated documentation in accordance with contract agreements and copyright laws; track the use of software and associated documentation protected by quantity licenses to control copying and distribution; and control and document the use of peer-to-peer file sharing technology to ensure that this capability is not used for the unauthorized distribution, display, performance, or reproduction of copyrighted work. |
  • License compliance running
| +| IA-2(12): Acceptance of PIV Credentials | Accept and electronically verify Personal Identity Verification (PIV) credentials. |
  • Auth SSO enabled
| +| IA-5(7): No Embedded Unencrypted Static Authenticators | Ensure that unencrypted static authenticators are not embedded in applications or other forms of static storage. |
  • Secret detection running
| +| IA-8(1): Acceptance of PIV Credentials From Other Agencies | Accept and electronically verify Personal Identity Verification (PIV) credentials from other federal agencies. |
  • Auth SSO enabled
| +| RA-5: Vulnerability Monitoring and Scanning | Scan for vulnerabilities in the system and hosted applications; employ vulnerability scanning tools and techniques; analyze vulnerability scan reports and results; remediate legitimate vulnerabilities; and share vulnerability information. |
  • Dependency scanning running
  • Container scanning running
  • DAST running
  • API security running
  • Fuzz testing running
| +| SA-11(1): Static Code Analysis | Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of the analysis. |
  • SAST running
| +| SA-11(8): Dynamic Code Analysis | Require the developer of the system, system component, or system service to employ dynamic code analysis tools to identify common flaws and document the results of the analysis. |
  • DAST running
  • Fuzz testing running
| + ## ISMAP compliance requirements The Information system Security Management and Assessment Program (ISMAP) aims to secure the security level of the government's cloud service procurement diff --git a/doc/user/duo_workflow/_index.md b/doc/user/duo_workflow/_index.md index aec3a052db6..3b86b85e782 100644 --- a/doc/user/duo_workflow/_index.md +++ b/doc/user/duo_workflow/_index.md @@ -10,7 +10,7 @@ title: GitLab Duo Workflow - Tier: Ultimate - Offering: GitLab.com - Status: Private beta -- LLM: Anthropic [Claude 3.5 Sonnet](https://console.cloud.google.com/vertex-ai/publishers/anthropic/model-garden/claude-3-5-sonnet) +- LLM: Anthropic [Claude Sonnet 4](https://www.anthropic.com/claude/sonnet) {{< /details >}} diff --git a/doc/user/duo_workflow/troubleshooting.md b/doc/user/duo_workflow/troubleshooting.md index ae756b994a9..d03257a99ca 100644 --- a/doc/user/duo_workflow/troubleshooting.md +++ b/doc/user/duo_workflow/troubleshooting.md @@ -2,7 +2,7 @@ stage: AI-powered group: Duo Workflow info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments -title: Troubleshoot GitLab Duo Workflow +title: Troubleshooting GitLab Duo Workflow --- {{< details >}} diff --git a/doc/user/gitlab_duo_chat/agentic_chat.md b/doc/user/gitlab_duo_chat/agentic_chat.md index 0b79dc83cf4..b928a4510b0 100644 --- a/doc/user/gitlab_duo_chat/agentic_chat.md +++ b/doc/user/gitlab_duo_chat/agentic_chat.md @@ -11,7 +11,7 @@ title: GitLab Duo Agentic Chat in VS Code - Add-on: GitLab Duo Core, Pro, or Enterprise - Offering: GitLab.com - Status: Experiment -- LLMs: Anthropic [Claude 3.7 Sonnet](https://console.cloud.google.com/vertex-ai/publishers/anthropic/model-garden/claude-3-7-sonnet) +- LLMs: Anthropic [Claude Sonnet 4](https://console.cloud.google.com/vertex-ai/publishers/anthropic/model-garden/claude-sonnet-4) {{< /details >}} diff --git a/doc/user/gitlab_duo_chat/troubleshooting.md b/doc/user/gitlab_duo_chat/troubleshooting.md index be375d04b86..84d60d72a26 100644 --- a/doc/user/gitlab_duo_chat/troubleshooting.md +++ b/doc/user/gitlab_duo_chat/troubleshooting.md @@ -2,7 +2,7 @@ stage: AI-powered group: Duo Chat info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments -title: GitLab Duo Chat troubleshooting +title: Troubleshooting GitLab Duo Chat --- When working with GitLab Duo Chat, you might encounter the following issues. diff --git a/doc/user/project/merge_requests/merge_request_troubleshooting.md b/doc/user/project/merge_requests/merge_request_troubleshooting.md index 399a52b8c44..da7ecbed1d0 100644 --- a/doc/user/project/merge_requests/merge_request_troubleshooting.md +++ b/doc/user/project/merge_requests/merge_request_troubleshooting.md @@ -3,7 +3,7 @@ stage: Create group: Code Review info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments description: Troubleshooting help for merge requests. -title: Merge request troubleshooting +title: Troubleshooting merge requests --- {{< details >}}