From 522f79601d9e6a86c8580b7cc254bf8d1954e8f6 Mon Sep 17 00:00:00 2001 From: Suzanne Selhorn Date: Mon, 14 Jul 2025 08:57:28 -0700 Subject: [PATCH 1/3] Updating bold nav items --- doc/development/ee_features.md | 4 +- doc/development/logs.md | 8 +- doc/install/aws/_index.md | 4 +- doc/install/azure/_index.md | 4 +- doc/install/install_ai_gateway.md | 2 +- .../compliance_security_policy_management.md | 8 +- .../hardening_application_recommendations.md | 8 +- doc/security/password_length_limits.md | 2 +- doc/security/reset_user_password.md | 2 +- doc/security/ssh_keys_restrictions.md | 2 +- doc/security/tokens/_index.md | 2 +- doc/security/two_factor_authentication.md | 10 +- doc/security/unlock_user.md | 2 +- doc/security/user_email_confirmation.md | 2 +- doc/security/user_file_uploads.md | 2 +- doc/security/webhooks.md | 10 +- doc/update/background_migrations.md | 6 +- foo.py | 250 ++++++++++++++++++ 18 files changed, 289 insertions(+), 39 deletions(-) create mode 100644 foo.py diff --git a/doc/development/ee_features.md b/doc/development/ee_features.md index 99e6b67cf09850..2ce01827e1f5dd 100644 --- a/doc/development/ee_features.md +++ b/doc/development/ee_features.md @@ -191,14 +191,14 @@ version of the product: only if the project namespace's plan includes the feature. 1. On the left sidebar, at the bottom, select **Admin**. - 1. On the left sidebar, select **Settings > General**. + 1. On the left sidebar, select **Settings** > **General**. 1. Expand **Account and limit**. 1. Select the **Allow use of licensed EE features** checkbox. 1. Select **Save changes**. 1. Ensure the group you want to test the EE feature for is actually using an EE plan: 1. On the left sidebar, at the bottom, select **Admin**. - 1. On the left sidebar, select **Overview > Groups**. + 1. On the left sidebar, select **Overview** > **Groups**. 1. Identify the group you want to modify, and select **Edit**. 1. Scroll to **Permissions and group features**. For **Plan**, select `Ultimate`. 1. Select **Save changes**. diff --git a/doc/development/logs.md b/doc/development/logs.md index 3ffbf920461803..f0728360aa6823 100644 --- a/doc/development/logs.md +++ b/doc/development/logs.md @@ -57,7 +57,7 @@ Prerequisites: 1. Create an access token: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Settings > Access tokens**. + 1. Select **Settings** > **Access tokens**. 1. Create an access token with the `api` scope and **Developer** role or greater. Save the access token value for later. 1. To configure your application to send GitLab logs, set the following environment variables: @@ -82,7 +82,7 @@ When you run your application, the OpenTelemetry exporter sends logs to GitLab. You can view the logs for a given project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor > Logs**. +1. Select **Monitor** > **Logs**. A list of logs is displayed. Currently log date, level, service, and message are supported. Select a log line to view its details. @@ -103,7 +103,7 @@ It is also possible to see log line details such as metadata and resource attrib You can create an issue to track any action taken to resolve or investigate a log. To create an issue for a log: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor > Logs**. +1. Select **Monitor** > **Logs**. 1. From the list of logs, select a log. 1. In the details drawer, select **Create issue**. @@ -113,7 +113,7 @@ You can edit the issue title and description. ### View issues related to a log 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor > Logs**. +1. Select **Monitor** > **Logs**. 1. From the list of logs, select a log. 1. In the details drawer, scroll to **Related issues**. 1. Optional. To view the issue details, select an issue. diff --git a/doc/install/aws/_index.md b/doc/install/aws/_index.md index d893bd66d7a0b5..bda805079bc525 100644 --- a/doc/install/aws/_index.md +++ b/doc/install/aws/_index.md @@ -239,7 +239,7 @@ it receive traffic from any destination. 1. Select **Route Tables** from the left menu and select the `gitlab-public` route to show the options at the bottom. -1. Select the **Routes** tab, select **Edit routes > Add route** and set `0.0.0.0/0` +1. Select the **Routes** tab, select **Edit routes** > **Add route** and set `0.0.0.0/0` as the destination. In the target column, select the **Internet Gateway** and select the `gitlab-gateway` we created previously. Select **Save changes** when done. @@ -568,7 +568,7 @@ Because we're adding our SSL certificate at the load balancer, we do not need th From your GitLab instance, connect to the RDS instance to verify access and to install the required `pg_trgm` and `btree_gist` extensions. -To find the host or endpoint, go to **Amazon RDS > Databases** and select the database you created earlier. Look for the endpoint under the **Connectivity & security** tab. +To find the host or endpoint, go to **Amazon RDS** > **Databases** and select the database you created earlier. Look for the endpoint under the **Connectivity & security** tab. Do not to include the colon and port number: diff --git a/doc/install/azure/_index.md b/doc/install/azure/_index.md index 35328eb0070640..9c04326926cfac 100644 --- a/doc/install/azure/_index.md +++ b/doc/install/azure/_index.md @@ -176,7 +176,7 @@ redirect you to the public IP. To set up the GitLab external URL: -1. Connect to GitLab through SSH by going to **Settings > Connect** from the VM +1. Connect to GitLab through SSH by going to **Settings** > **Connect** from the VM dashboard, and follow the instructions. Remember to sign in with the username and SSH key you specified when you [created the VM](#configure-the-basics-tab). The Azure VM domain name is the one you @@ -258,7 +258,7 @@ in this section whenever you need to update GitLab. To determine the version of GitLab you're currently running: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Overview > Dashboard**. +1. Select **Overview** > **Dashboard**. 1. Find the version under the **Components** table. If there's a newer available version of GitLab that contains one or more diff --git a/doc/install/install_ai_gateway.md b/doc/install/install_ai_gateway.md index 9e587f640a871f..d3f8049f80732e 100644 --- a/doc/install/install_ai_gateway.md +++ b/doc/install/install_ai_gateway.md @@ -371,7 +371,7 @@ If access issues persist, check that authentication is correctly configured, and In case of persistent issues, the error message may suggest bypassing authentication with `AIGW_AUTH__BYPASS_EXTERNAL=true`, but only do this for troubleshooting. -You can also run a [health check](../user/gitlab_duo/setup.md#run-a-health-check-for-gitlab-duo) by going to **Admin > GitLab Duo**. +You can also run a [health check](../user/gitlab_duo/setup.md#run-a-health-check-for-gitlab-duo) by going to **Admin** > **GitLab Duo**. These tests are performed for offline environments: diff --git a/doc/security/compliance_security_policy_management.md b/doc/security/compliance_security_policy_management.md index 7486ff5fa40e22..46f87453ae4369 100644 --- a/doc/security/compliance_security_policy_management.md +++ b/doc/security/compliance_security_policy_management.md @@ -53,7 +53,7 @@ You can designate a CSP group using either the GitLab UI or the REST API. #### Using the GitLab UI -1. Go to **Admin Area** > **Settings** > **Security and Compliance**. +1. Go to **Admin Area**** > ****Settings**** > ****Security and Compliance**. 1. In the **Designate CSP Group** section, select an existing top-level group from the dropdown list. 1. Select **Save changes**. @@ -113,7 +113,7 @@ Instance administrators can: Group administrators and owners can: -- View all applicable policies in **Secure** > **Policies**, including both locally-defined and centrally-managed policies. +- View all applicable policies in **Secure**** > ****Policies**, including both locally-defined and centrally-managed policies. - Create team-specific policies in addition to centrally-managed ones. - Understand policy sources with clear indicators that show whether policies come from your team or central administration. @@ -127,7 +127,7 @@ The **Policies** page displays only the policies from the CSP that are currently Project administrators and owners can: -- View all applicable policies in **Secure** > **Policies**, including both locally-defined and centrally-managed policies. +- View all applicable policies in **Secure**** > ****Policies**, including both locally-defined and centrally-managed policies. - Create project-specific policies in addition to centrally-managed ones. - Understand policy sources with clear indicators that show whether policies come from your project, group, or central administration. @@ -141,7 +141,7 @@ The **Policies** page displays only the policies from the CSP that are currently Developers can: -- View all security policies that apply to your work in the **Secure** > **Policies**. +- View all security policies that apply to your work in the **Secure**** > ****Policies**. - Understand security and compliance requirements with clear visibility into centrally-mandated policies. ## Beta considerations diff --git a/doc/security/hardening_application_recommendations.md b/doc/security/hardening_application_recommendations.md index ad818b45d4e5ba..5dc58888e3450d 100644 --- a/doc/security/hardening_application_recommendations.md +++ b/doc/security/hardening_application_recommendations.md @@ -57,7 +57,7 @@ the documentation on [deploy keys](../user/project/deploy_keys/_index.md) and ## General 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. Hardening adjustments can be made in 4 sections. @@ -175,7 +175,7 @@ For more detailed information, see ## Integrations 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Integrations**. +1. Select **Settings** > **Integrations**. In general, as long as administrators control and monitor usage, integrations are fine in a hardened environment. Be cautious about integrations that allow @@ -186,7 +186,7 @@ process or authenticated user. ## Metrics and profiling 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Metrics and profiling**. +1. Select **Settings** > **Metrics and profiling**. The main focus for hardening is **Usage statistics**: @@ -201,7 +201,7 @@ The main focus for hardening is **Usage statistics**: ## Network 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Network**. +1. Select **Settings** > **Network**. For any setting that enables rate limiting, make sure it is selected. Default values should be fine. Additionally there are numerous settings that enable access, and all diff --git a/doc/security/password_length_limits.md b/doc/security/password_length_limits.md index 77c7898d307aac..ecc708021d2a29 100644 --- a/doc/security/password_length_limits.md +++ b/doc/security/password_length_limits.md @@ -28,7 +28,7 @@ The user password length is set to a minimum of 8 characters by default. To change the minimum password length using GitLab UI: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Sign-up restrictions**. 1. Enter a **Minimum password length** value greater than or equal to `8`. 1. Select **Save changes**. diff --git a/doc/security/reset_user_password.md b/doc/security/reset_user_password.md index 3a2ded7c06646b..e2250e92b11a5d 100644 --- a/doc/security/reset_user_password.md +++ b/doc/security/reset_user_password.md @@ -25,7 +25,7 @@ You can reset user passwords by using the UI, a Rake task, a Rails console, or t To reset a user password in the UI: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Overview > Users**. +1. Select **Overview** > **Users**. 1. Identify a user account to update, select **Edit**. 1. In the **Password** section, enter and confirm a new password. 1. Select **Save changes**. diff --git a/doc/security/ssh_keys_restrictions.md b/doc/security/ssh_keys_restrictions.md index 56c434d86dccf0..3c0b180863dadb 100644 --- a/doc/security/ssh_keys_restrictions.md +++ b/doc/security/ssh_keys_restrictions.md @@ -27,7 +27,7 @@ GitLab allows you to restrict the allowed SSH key technology as well as specify the minimum key length for each technology: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General** . +1. Select **Settings** > **General** . 1. Expand **Visibility and access controls** and set your desired values for each key type: - **RSA SSH keys**. - **DSA SSH keys**. diff --git a/doc/security/tokens/_index.md b/doc/security/tokens/_index.md index 68413a3fbe89b9..a63bd9316e09e1 100644 --- a/doc/security/tokens/_index.md +++ b/doc/security/tokens/_index.md @@ -297,7 +297,7 @@ Prerequisites: - You must be an administrator. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility and access controls**. 1. Under **Feed token**, select the **Disable feed token** checkbox, then select **Save changes**. diff --git a/doc/security/two_factor_authentication.md b/doc/security/two_factor_authentication.md index a747bb6b2414f1..30c8370d1eb407 100644 --- a/doc/security/two_factor_authentication.md +++ b/doc/security/two_factor_authentication.md @@ -50,7 +50,7 @@ You can use the UI or the API to enforce 2FA for all users. ### Use the UI 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Sign-in restrictions**: - Select **Enforce two-factor authentication** to enable this feature. - In **Two-factor grace period**, enter a number of hours. If you want to @@ -83,7 +83,7 @@ For more information, see the [list of settings that can be accessed through API Administrators can enforce 2FA for administrator users in a GitLab Self-Managed instance. 1. On the left sidebar, at the bottom, select **Admin**. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, select **Settings** > **General**. 1. Expand the **Sign-in restrictions** section: 1. Select **Require administrators to enable 2FA**. 1. In **Two-factor grace period**, enter a number of hours. If you want to @@ -121,7 +121,7 @@ Prerequisites: To enforce 2FA for a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. Select **All users in this group must set up two-factor authentication**. 1. Optional. In **Delay 2FA enforcement (hours)**, enter the number of hours you @@ -148,7 +148,7 @@ In such cases, the most restrictive requirement takes precedence. To prevent subgroups from setting individual 2FA requirements: -1. Go to the top-level group's **Settings > General**. +1. Go to the top-level group's **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Clear the **Allow subgroups to set up their own two-factor authentication rule** checkbox. @@ -250,7 +250,7 @@ Top-level group Owners can disable two-factor authentication (2FA) for enterpris To disable 2FA: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. 1. Find a user with the **Enterprise** and **2FA** badges. 1. Select **More actions** ({{< icon name="ellipsis_v" >}}) and select **Disable two-factor authentication**. diff --git a/doc/security/unlock_user.md b/doc/security/unlock_user.md index 76b1b1a54bb539..913207fdcf4ec7 100644 --- a/doc/security/unlock_user.md +++ b/doc/security/unlock_user.md @@ -53,7 +53,7 @@ Prerequisites To unlock an account from the Admin area: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Overview > Users**. +1. Select **Overview** > **Users**. 1. Use the search bar to find the locked user. 1. From the **User administration** dropdown list, select **Unlock**. diff --git a/doc/security/user_email_confirmation.md b/doc/security/user_email_confirmation.md index 548abf04754711..25bd8a9c3d1c2c 100644 --- a/doc/security/user_email_confirmation.md +++ b/doc/security/user_email_confirmation.md @@ -17,7 +17,7 @@ the user signs up. When this setting is enabled, the user is unable to sign in u they confirm their email address. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Sign-up restrictions** and look for the **Email confirmation settings** options. ## Confirmation token expiry diff --git a/doc/security/user_file_uploads.md b/doc/security/user_file_uploads.md index 57c65541b4bfd3..cb841d7b57b73c 100644 --- a/doc/security/user_file_uploads.md +++ b/doc/security/user_file_uploads.md @@ -64,7 +64,7 @@ Prerequisites: To configure authentication settings for all media files: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. Scroll to **Project visibility** and select **Require authentication to view media files**. diff --git a/doc/security/webhooks.md b/doc/security/webhooks.md index 5eadc83e75941d..0fe49e7e65ddfd 100644 --- a/doc/security/webhooks.md +++ b/doc/security/webhooks.md @@ -56,7 +56,7 @@ To prevent exploitation of insecure internal web services, all webhook and integ To allow access to these addresses: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Network**. +1. Select **Settings** > **Network**. 1. Expand **Outbound requests**. 1. Select the **Allow requests to the local network from webhooks and integrations** checkbox. @@ -69,7 +69,7 @@ Prerequisites: [System hooks](../administration/system_hooks.md) can make requests to the local network by default. To prevent system hook requests to the local network: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Network**. +1. Select **Settings** > **Network**. 1. Expand **Outbound requests**. 1. Clear the **Allow requests to the local network from system hooks** checkbox. @@ -82,7 +82,7 @@ Prerequisites: [DNS rebinding](https://en.wikipedia.org/wiki/DNS_rebinding) is a technique to make a malicious domain name resolve to an internal network resource to bypass local network access restrictions. GitLab has protection against this attack enabled by default. To disable this protection: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Network**. +1. Select **Settings** > **Network**. 1. Expand **Outbound requests**. 1. Clear the **Enforce DNS-rebinding attack protection** checkbox. @@ -101,7 +101,7 @@ Prerequisites: To filter requests by blocking many requests: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Network**. +1. Select **Settings** > **Network**. 1. Expand **Outbound requests**. 1. Select the **Block all requests, except for IP addresses, IP ranges, and domain names defined in the allowlist** checkbox. @@ -124,7 +124,7 @@ Prerequisites: To allow outbound requests to certain IP addresses and domains: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Network**. +1. Select **Settings** > **Network**. 1. Expand **Outbound requests**. 1. In **Local IP addresses and domain names that hooks and integrations can access**, enter your IP addresses and domains. diff --git a/doc/update/background_migrations.md b/doc/update/background_migrations.md index ed67d4ba8da0e3..f8e76326cfc860 100644 --- a/doc/update/background_migrations.md +++ b/doc/update/background_migrations.md @@ -81,7 +81,7 @@ Prerequisites: To check the status of batched background migrations: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Monitoring > Background migrations**. +1. Select **Monitoring** > **Background migrations**. 1. Select **Queued** or **Finalizing** to see incomplete migrations, and **Failed** for failed migrations. @@ -257,7 +257,7 @@ Prerequisites: - You must have administrator access to the instance. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Monitoring > Background migrations**. +1. Select **Monitoring** > **Background migrations**. 1. Select the **Failed** tab. This displays a list of failed batched background migrations. 1. Select the failed **Migration** to see the migration parameters and the jobs that failed. 1. Under **Failed jobs**, select each **ID** to see why the job failed. @@ -272,7 +272,7 @@ Prerequisites: - You must have administrator access to the instance. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Monitoring > Background migrations**. +1. Select **Monitoring** > **Background migrations**. 1. Select the **Failed** tab. This displays a list of failed batched background migrations. 1. Select a failed batched background migration to retry by clicking on the retry button ({{< icon name="retry" >}}). diff --git a/foo.py b/foo.py new file mode 100644 index 00000000000000..b88fe3edac7c62 --- /dev/null +++ b/foo.py @@ -0,0 +1,250 @@ +#!/usr/bin/env python3 +""" +GitLab Markdown Bold Formatter +Fixes bold formatting around the '>' character in GitLab documentation. +Moves '>' outside of bold formatting to comply with style guidelines. +""" + +import os +import re +import glob +from pathlib import Path +from typing import List, Tuple, Dict + +def find_markdown_files(root_dir: str) -> List[str]: + """Find all markdown files in the directory and subdirectories.""" + pattern = os.path.join(root_dir, '**', '*.md') + return glob.glob(pattern, recursive=True) + +def should_skip_line(line: str) -> bool: + """ + Check if a line should be skipped from processing. + + Skip: + - Lines inside code blocks (```...```) + - Lines with alerts like {{< alert type="note" >}} + - Lines with tab titles like {{< tab title="Enterprise Edition" >}} + """ + # Check for alerts + if re.search(r'\{\{<\s*alert\s+.*>\}\}', line): + return True + + # Check for tab titles + if re.search(r'\{\{<\s*tab\s+title=.*>\}\}', line): + return True + + return False + +def fix_bold_formatting(content: str) -> Tuple[str, int]: + """ + Fix bold formatting around '>' character. + + Only fixes this pattern: + - **text > text** -> **text** > **text** + + Skips: + - Code blocks + - Alert shortcodes + - Tab title shortcodes + + Returns: (fixed_content, number_of_changes) + """ + changes = 0 + lines = content.split('\n') + in_code_block = False + processed_lines = [] + + for line in lines: + # Track code block state + if line.strip().startswith('```'): + in_code_block = not in_code_block + processed_lines.append(line) + continue + + # Skip processing if we're in a code block or this line should be skipped + if in_code_block or should_skip_line(line): + processed_lines.append(line) + continue + + # Process the line for bold formatting fixes + original_line = line + + # Only Pattern: **text > text** -> **text** > **text** + # This handles cases like **Overview > Users** but avoids HTML/markdown syntax + # More specific pattern that requires word characters and avoids HTML tags + pattern = r'\*\*([A-Za-z0-9\s]+?)\s*>\s*([A-Za-z0-9\s]+?)\*\*' + def replace_pattern(match): + nonlocal changes + # Additional check to avoid HTML/markdown syntax + left_part = match.group(1).strip() + right_part = match.group(2).strip() + + # Skip if it looks like HTML or contains special characters that suggest it's not UI navigation + if ('<' in left_part or '>' in left_part or + '<' in right_part or '>' in right_part or + left_part.endswith('br') or + '[' in left_part or ']' in left_part or + '[' in right_part or ']' in right_part): + return match.group(0) # Return original match unchanged + + changes += 1 + return f'**{left_part}** > **{right_part}**' + + line = re.sub(pattern, replace_pattern, line) + + processed_lines.append(line) + + return '\n'.join(processed_lines), changes + +def process_file(filepath: str) -> Dict[str, any]: + """Process a single markdown file.""" + try: + with open(filepath, 'r', encoding='utf-8') as f: + original_content = f.read() + + fixed_content, changes = fix_bold_formatting(original_content) + + if changes > 0: + # Write fixed content + with open(filepath, 'w', encoding='utf-8') as f: + f.write(fixed_content) + + return { + 'filepath': filepath, + 'changes': changes, + 'status': 'modified' + } + else: + return { + 'filepath': filepath, + 'changes': 0, + 'status': 'no_changes' + } + + except Exception as e: + return { + 'filepath': filepath, + 'changes': 0, + 'status': 'error', + 'error': str(e) + } + +def process_batch(files: List[str], batch_num: int) -> Dict[str, any]: + """Process a batch of files.""" + print(f"\nProcessing batch {batch_num} ({len(files)} files)...") + + results = { + 'batch_num': batch_num, + 'files_processed': 0, + 'files_modified': 0, + 'total_changes': 0, + 'errors': [], + 'modified_files': [] + } + + for filepath in files: + result = process_file(filepath) + results['files_processed'] += 1 + + if result['status'] == 'modified': + results['files_modified'] += 1 + results['total_changes'] += result['changes'] + results['modified_files'].append({ + 'file': result['filepath'], + 'changes': result['changes'] + }) + print(f" ✓ {result['filepath']} ({result['changes']} changes)") + + elif result['status'] == 'error': + results['errors'].append({ + 'file': result['filepath'], + 'error': result['error'] + }) + print(f" ✗ {result['filepath']} (ERROR: {result['error']})") + + else: + print(f" - {result['filepath']} (no changes needed)") + + return results + +def main(): + # Configuration + ROOT_DIR = "/Users/sselhorn/dev/gitlab/gitlab/doc" + BATCH_SIZE = 50 + + print("GitLab Markdown Bold Formatter") + print("=" * 40) + print(f"Root directory: {ROOT_DIR}") + print(f"Batch size: {BATCH_SIZE}") + + # Verify directory exists + if not os.path.exists(ROOT_DIR): + print(f"Error: Directory {ROOT_DIR} does not exist!") + return + + # Find all markdown files + print("\nFinding markdown files...") + markdown_files = find_markdown_files(ROOT_DIR) + + if not markdown_files: + print("No markdown files found!") + return + + print(f"Found {len(markdown_files)} markdown files") + + # Process confirmation + response = input(f"\nDo you want to process these files? (y/N): ") + if response.lower() != 'y': + print("Operation cancelled.") + return + + # Process files in batches + all_results = [] + total_files = len(markdown_files) + + for i in range(0, total_files, BATCH_SIZE): + batch = markdown_files[i:i + BATCH_SIZE] + batch_num = (i // BATCH_SIZE) + 1 + + result = process_batch(batch, batch_num) + all_results.append(result) + + # Show batch summary + print(f"Batch {batch_num} complete: {result['files_modified']}/{result['files_processed']} files modified, {result['total_changes']} total changes") + + # Ask to continue if there are more batches + if i + BATCH_SIZE < total_files: + response = input(f"\nContinue with next batch? (Y/n): ") + if response.lower() == 'n': + print("Processing stopped by user.") + break + + # Final summary + print("\n" + "=" * 40) + print("FINAL SUMMARY") + print("=" * 40) + + total_processed = sum(r['files_processed'] for r in all_results) + total_modified = sum(r['files_modified'] for r in all_results) + total_changes = sum(r['total_changes'] for r in all_results) + total_errors = sum(len(r['errors']) for r in all_results) + + print(f"Files processed: {total_processed}") + print(f"Files modified: {total_modified}") + print(f"Total changes: {total_changes}") + print(f"Errors: {total_errors}") + + if total_modified > 0: + print(f"\nModified files:") + for result in all_results: + for mod_file in result['modified_files']: + print(f" {mod_file['file']} ({mod_file['changes']} changes)") + + if total_errors > 0: + print(f"\nErrors occurred:") + for result in all_results: + for error in result['errors']: + print(f" {error['file']}: {error['error']}") + +if __name__ == "__main__": + main() \ No newline at end of file -- GitLab From 75602b4bf5fb36e478d6c14ed88c6b65950f3862 Mon Sep 17 00:00:00 2001 From: Suzanne Selhorn Date: Mon, 14 Jul 2025 09:01:21 -0700 Subject: [PATCH 2/3] A bunch more --- doc/ci/caching/_index.md | 2 +- .../bitbucket_integration.md | 2 +- .../github_integration.md | 4 +- doc/ci/cloud_deployment/_index.md | 2 +- .../cloud_deployment/ecs/deploy_to_aws_ecs.md | 14 +++--- doc/ci/components/_index.md | 2 +- doc/ci/environments/_index.md | 16 +++---- doc/ci/environments/deployment_approvals.md | 6 +-- doc/ci/environments/deployments.md | 2 +- doc/ci/environments/kubernetes_dashboard.md | 8 ++-- doc/ci/examples/semantic-release.md | 2 +- doc/ci/jobs/_index.md | 10 ++-- doc/ci/jobs/ci_job_token.md | 2 +- doc/ci/jobs/job_artifacts.md | 4 +- doc/ci/jobs/job_rules.md | 2 +- .../mobile_devops_tutorial_android.md | 2 +- .../mobile_devops_tutorial_ios.md | 2 +- doc/ci/pipeline_editor/_index.md | 6 +-- doc/ci/pipelines/_index.md | 6 +-- ...dedicated_hosted_runner_compute_minutes.md | 2 +- .../instance_runner_compute_minutes.md | 2 +- doc/ci/pipelines/merge_trains.md | 6 +-- doc/ci/pipelines/merged_results_pipelines.md | 2 +- doc/ci/pipelines/schedules.md | 8 ++-- doc/ci/pipelines/settings.md | 4 +- doc/ci/quick_start/_index.md | 4 +- doc/ci/quick_start/tutorial.md | 4 +- doc/ci/review_apps/_index.md | 8 ++-- doc/ci/runners/configure_runners.md | 6 +-- .../runners/runner_fleet_dashboard_groups.md | 2 +- doc/ci/runners/runners_scope.md | 14 +++--- doc/ci/secrets/fortanix_dsm_integration.md | 6 +-- doc/ci/secrets/gcp_secret_manager.md | 2 +- doc/ci/test_cases/_index.md | 6 +-- doc/ci/testing/code_coverage/_index.md | 6 +-- doc/ci/triggers/_index.md | 2 +- doc/ci/yaml/_index.md | 2 +- doc/ci/yaml/deprecated_keywords.md | 2 +- doc/ci/yaml/lint.md | 4 +- .../ai_features/ai_development_license.md | 6 +-- .../ai_features/amazon_q_integration.md | 2 +- doc/development/cicd/schema.md | 2 +- .../configure-dev-env-gdk-in-a-box.md | 8 ++-- .../first_contribution/contribute-web-ide.md | 2 +- doc/development/documentation/_index.md | 6 +-- .../documentation/styleguide/_index.md | 14 +++--- .../documentation/styleguide/word_list.md | 4 +- doc/development/ee_features.md | 4 +- doc/development/integrations/jenkins.md | 2 +- doc/development/integrations/jira_connect.md | 2 +- .../local_setup_and_debugging.md | 2 +- .../internal_analytics/product_analytics.md | 12 ++--- doc/development/logs.md | 8 ++-- doc/development/metrics.md | 8 ++-- doc/development/tracing.md | 8 ++-- doc/install/aws/_index.md | 4 +- doc/install/azure/_index.md | 4 +- doc/install/install_ai_gateway.md | 2 +- .../advanced_search/elasticsearch.md | 28 +++++------ doc/integration/akismet.md | 2 +- doc/integration/datadog.md | 2 +- doc/integration/diffblue_cover.md | 2 +- .../elasticsearch/troubleshooting/access.md | 2 +- .../elasticsearch/troubleshooting/indexing.md | 2 +- doc/integration/exact_code_search/zoekt.md | 22 ++++----- doc/integration/external-issue-tracker.md | 2 +- doc/integration/gitpod.md | 6 +-- doc/integration/google_cloud_iam.md | 4 +- doc/integration/jenkins.md | 6 +-- doc/integration/jira/configure.md | 6 +-- doc/integration/jira/connect-app.md | 16 +++---- doc/integration/jira/dvcs/troubleshooting.md | 4 +- doc/integration/jira/issues.md | 6 +-- doc/integration/kerberos.md | 4 +- doc/integration/mattermost/_index.md | 8 ++-- doc/integration/oauth_provider.md | 2 +- doc/integration/omniauth.md | 2 +- doc/integration/recaptcha.md | 2 +- doc/integration/snowflake.md | 6 +-- doc/integration/sourcegraph.md | 2 +- .../compliance_security_policy_management.md | 8 ++-- .../hardening_application_recommendations.md | 8 ++-- doc/security/password_length_limits.md | 2 +- doc/security/reset_user_password.md | 2 +- doc/security/ssh_keys_restrictions.md | 2 +- doc/security/tokens/_index.md | 2 +- doc/security/two_factor_authentication.md | 10 ++-- doc/security/unlock_user.md | 2 +- doc/security/user_email_confirmation.md | 2 +- doc/security/user_file_uploads.md | 2 +- doc/security/webhooks.md | 10 ++-- doc/solutions/components/jira_dora.md | 6 +-- doc/solutions/components/jira_vsa.md | 10 ++-- doc/solutions/components/oss_license_check.md | 6 +-- doc/solutions/components/secret_detection.md | 2 +- doc/solutions/components/securitykpi.md | 2 +- doc/update/background_migrations.md | 6 +-- .../api_fuzzing/_index.md | 2 +- .../configuration/enabling_the_analyzer.md | 4 +- .../api_fuzzing/create_har_files.md | 8 ++-- .../api_security_testing/_index.md | 2 +- .../configuration/enabling_the_analyzer.md | 2 +- .../container_scanning/_index.md | 8 ++-- .../coverage_fuzzing/_index.md | 6 +-- .../dast/browser/_index.md | 2 +- .../application_security/dast/profiles.md | 22 ++++----- .../dependency_list/_index.md | 6 +-- .../dependency_scanning/_index.md | 8 ++-- .../detect/roll_out_security_scanning.md | 8 ++-- .../detect/security_configuration.md | 4 +- .../detect/security_scanning_results.md | 8 ++-- .../iac_scanning/_index.md | 4 +- .../application_security/policies/_index.md | 4 +- .../centralized_security_policy_management.md | 6 +-- .../merge_request_approval_policies.md | 4 +- .../policies/pipeline_execution_policies.md | 8 ++-- .../scheduled_pipeline_execution_policies.md | 4 +- .../policies/security_policy_projects.md | 2 +- .../vulnerability_management_policy.md | 4 +- doc/user/application_security/sast/_index.md | 6 +-- .../sast/gitlab_advanced_sast.md | 4 +- .../secret_detection/exclusions.md | 2 +- .../secret_detection/pipeline/_index.md | 6 +-- .../push_protection_tutorial.md | 2 +- .../secret_push_protection/_index.md | 4 +- .../security_dashboard/_index.md | 8 ++-- .../security_inventory/_index.md | 2 +- .../vulnerabilities/_index.md | 18 ++++---- .../vulnerability_archival/_index.md | 2 +- .../vulnerability_report/_index.md | 16 +++---- doc/user/clusters/agent/ci_cd_workflow.md | 2 +- doc/user/clusters/agent/getting_started.md | 2 +- .../agent/getting_started_deployments.md | 4 +- doc/user/clusters/agent/install/_index.md | 2 +- doc/user/clusters/agent/user_access.md | 2 +- doc/user/clusters/agent/vulnerabilities.md | 2 +- doc/user/clusters/agent/work_with_agent.md | 10 ++-- doc/user/clusters/management_project.md | 2 +- doc/user/compliance/audit_event_streaming.md | 30 ++++++------ doc/user/compliance/audit_events.md | 6 +-- .../compliance_chain_of_custody_report.md | 4 +- .../compliance_frameworks_report.md | 14 +++--- .../compliance_projects_report.md | 20 ++++---- ...ompliance_standards_adherence_dashboard.md | 4 +- .../compliance_status_report.md | 4 +- .../compliance_violations_report.md | 6 +-- .../compliance_frameworks/_index.md | 18 ++++---- doc/user/compliance/compliance_pipelines.md | 4 +- .../compliance/license_approval_policies.md | 2 +- doc/user/crm/_index.md | 24 +++++----- doc/user/custom_roles/_index.md | 18 ++++---- doc/user/discussions/_index.md | 12 ++--- .../software_development_flow.md | 4 +- .../duo_agent_platform/troubleshooting.md | 4 +- doc/user/free_user_limit.md | 2 +- doc/user/gitlab_duo/context_exclusion.md | 2 +- .../model_context_protocol/_index.md | 2 +- doc/user/gitlab_duo/model_selection.md | 2 +- doc/user/gitlab_duo/turn_on_off.md | 18 ++++---- doc/user/gitlab_duo/turn_on_off_earlier.md | 18 ++++---- .../tutorials/fix_code_python_shop.md | 2 +- doc/user/gitlab_duo_chat/_index.md | 8 ++-- doc/user/gitlab_duo_chat/agentic_chat.md | 2 +- doc/user/gitlab_duo_chat/examples.md | 2 +- doc/user/gitlab_duo_chat/turn_on_off.md | 2 +- doc/user/group/_index.md | 26 +++++------ doc/user/group/access_and_permissions.md | 18 ++++---- doc/user/group/clusters/_index.md | 4 +- .../group/contribution_analytics/_index.md | 2 +- doc/user/group/custom_project_templates.md | 2 +- doc/user/group/devops_adoption/_index.md | 6 +-- doc/user/group/epics/epic_boards.md | 6 +-- doc/user/group/epics/manage_epics.md | 22 ++++----- doc/user/group/import/troubleshooting.md | 2 +- doc/user/group/issues_analytics/_index.md | 2 +- doc/user/group/iterations/_index.md | 20 ++++---- doc/user/group/manage.md | 44 +++++++++--------- doc/user/group/moderate_users.md | 6 +-- .../group/reporting/git_abuse_rate_limit.md | 2 +- .../group/repositories_analytics/_index.md | 2 +- doc/user/group/roadmap/_index.md | 2 +- doc/user/group/saml_sso/_index.md | 18 ++++---- doc/user/group/saml_sso/group_sync.md | 10 ++-- doc/user/group/saml_sso/scim_setup.md | 2 +- doc/user/group/saml_sso/troubleshooting.md | 2 +- .../group/settings/group_access_tokens.md | 6 +-- doc/user/group/ssh_certificates.md | 2 +- doc/user/group/subgroups/_index.md | 6 +-- .../group/value_stream_analytics/_index.md | 20 ++++---- doc/user/okrs.md | 14 +++--- doc/user/organization/_index.md | 14 +++--- doc/user/permissions.md | 2 +- doc/user/project/badges.md | 12 ++--- doc/user/project/canary_deployments.md | 4 +- doc/user/project/code_intelligence.md | 4 +- doc/user/project/deploy_boards.md | 2 +- doc/user/project/description_templates.md | 12 ++--- doc/user/project/file_lock.md | 4 +- doc/user/project/insights/_index.md | 4 +- doc/user/project/issue_board.md | 2 +- doc/user/project/labels.md | 24 +++++----- doc/user/project/project_topics.md | 2 +- doc/user/project/protected_tags.md | 8 ++-- doc/user/project/releases/_index.md | 16 +++---- doc/user/project/repository/_index.md | 2 +- .../project/repository/branches/default.md | 12 ++--- .../repository/code_suggestions/_index.md | 8 ++-- .../repository/code_suggestions/set_up.md | 2 +- .../code_suggestions/supported_extensions.md | 4 +- .../code_suggestions/troubleshooting.md | 16 +++---- doc/user/project/repository/commits/_index.md | 22 ++++----- doc/user/project/repository/files/_index.md | 2 +- .../project/repository/files/git_blame.md | 4 +- .../project/repository/files/git_history.md | 2 +- .../project/repository/forking_workflow.md | 2 +- doc/user/project/repository/push_rules.md | 4 +- .../project/repository/repository_size.md | 6 +-- .../repository/signed_commits/_index.md | 4 +- doc/user/project/repository/tags/_index.md | 6 +-- doc/user/project/repository/web_editor.md | 6 +-- doc/user/project/settings/_index.md | 16 +++---- doc/user/project/settings/import_export.md | 6 +-- .../project/settings/project_access_tokens.md | 6 +-- doc/user/project/system_notes.md | 6 +-- doc/user/project/time_tracking.md | 2 +- doc/user/project/working_with_projects.md | 18 ++++---- doc/user/public_access.md | 6 +-- doc/user/search/_index.md | 6 +-- doc/user/shortcuts.md | 46 +++++++++---------- doc/user/snippets.md | 8 ++-- doc/user/storage_usage_quotas.md | 4 +- doc/user/tasks.md | 42 ++++++++--------- doc/user/version.md | 2 +- doc/user/workspace/_index.md | 2 +- doc/user/workspace/configuration.md | 6 +-- .../workspace/gitlab_agent_configuration.md | 8 ++-- .../set_up_gitlab_agent_and_proxies.md | 2 +- doc/user/workspace/set_up_infrastructure.md | 6 +-- .../workspace/workspaces_troubleshooting.md | 2 +- 239 files changed, 806 insertions(+), 806 deletions(-) diff --git a/doc/ci/caching/_index.md b/doc/ci/caching/_index.md index 4657b73d611af6..04efcb2843ee49 100644 --- a/doc/ci/caching/_index.md +++ b/doc/ci/caching/_index.md @@ -696,7 +696,7 @@ The next time the pipeline runs, the cache is stored in a different location. You can clear the cache in the GitLab UI: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. In the upper-right corner, select **Clear runner caches**. On the next commit, your CI/CD jobs use a new cache. diff --git a/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md b/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md index 954344aba95c95..7eeb172c71821e 100644 --- a/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md +++ b/doc/ci/ci_cd_for_external_repos/bitbucket_integration.md @@ -45,7 +45,7 @@ To use GitLab CI/CD with a Bitbucket Cloud repository: with `api` scope. The token is used to authenticate requests from the web hook that is created in Bitbucket to notify GitLab of new commits. -1. In Bitbucket, from **Settings > Webhooks**, create a new webhook to notify +1. In Bitbucket, from **Settings** > **Webhooks**, create a new webhook to notify GitLab of new commits. The webhook URL should be set to the GitLab API to trigger pull mirroring, diff --git a/doc/ci/ci_cd_for_external_repos/github_integration.md b/doc/ci/ci_cd_for_external_repos/github_integration.md index e8ec6c1f10a2f4..dc0a06544f9734 100644 --- a/doc/ci/ci_cd_for_external_repos/github_integration.md +++ b/doc/ci/ci_cd_for_external_repos/github_integration.md @@ -76,12 +76,12 @@ To manually enable GitLab CI/CD for your repository: 1. Fill in all the other fields and select **Create project**. GitLab automatically configures polling-based pull mirroring. 1. In GitLab, enable [GitHub project integration](../../user/project/integrations/github.md): - 1. On the left sidebar, select **Settings > Integrations**. + 1. On the left sidebar, select **Settings** > **Integrations**. 1. Select the **Active** checkbox. 1. Paste your personal access token and HTTPS repository URL into the form and select **Save**. 1. In GitLab, create a personal access token with `API` scope to authenticate the GitHub web hook notifying GitLab of new commits. -1. In GitHub, from **Settings > Webhooks**, create a web hook to notify GitLab of +1. In GitHub, from **Settings** > **Webhooks**, create a web hook to notify GitLab of new commits. The web hook URL should be set to the GitLab API to diff --git a/doc/ci/cloud_deployment/_index.md b/doc/ci/cloud_deployment/_index.md index 97cc8cc3849f6c..438bb70ea56149 100644 --- a/doc/ci/cloud_deployment/_index.md +++ b/doc/ci/cloud_deployment/_index.md @@ -34,7 +34,7 @@ After you set up authentication, you can configure CI/CD to deploy. 1. Sign on to your AWS account. 1. Create [an IAM user](https://console.aws.amazon.com/iam/home#/home). -1. Select your user to access its details. Go to **Security credentials > Create a new access key**. +1. Select your user to access its details. Go to **Security credentials** > **Create a new access key**. 1. Note the **Access key ID** and **Secret access key**. 1. In your GitLab project, go to **Settings > CI/CD**. Set the following [CI/CD variables](../variables/_index.md): diff --git a/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md b/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md index 745143e21039f7..fe8d7256f47bd6 100644 --- a/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md +++ b/doc/ci/cloud_deployment/ecs/deploy_to_aws_ecs.md @@ -77,7 +77,7 @@ and [Container Registry](../../../user/packages/container_registry/_index.md). 1. Select **Commit Changes**. It automatically triggers a new pipeline. In this pipeline, the `build` job containerizes the application and pushes the image to [GitLab container registry](../../../user/packages/container_registry/_index.md). -1. Visit **Deploy > Container Registry**. Make sure the application image has been +1. Visit **Deploy** > **Container Registry**. Make sure the application image has been pushed. ![A containerized application image in the GitLab container registry.](img/registry_v13_10.png) @@ -93,15 +93,15 @@ later. [ECS Task definitions](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definitions.html) is a specification about how the application image is started by an [ECS service](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html). -1. Go to **ECS > Task Definitions** on [AWS console](https://aws.amazon.com/). +1. Go to **ECS** > **Task Definitions** on [AWS console](https://aws.amazon.com/). 1. Select **Create new Task Definition**. ![Task definitions page with a 'Create new task definition' button.](img/ecs-task-definitions_v13_10.png) 1. Choose **EC2** as the launch type. Select **Next Step**. 1. Set `ecs_demo` to **Task Definition Name**. -1. Set `512` to **Task Size > Task memory** and **Task CPU**. -1. Select **Container Definitions > Add container**. This opens a container registration form. +1. Set `512` to **Task Size** > **Task memory** and **Task CPU**. +1. Select **Container Definitions** > **Add container**. This opens a container registration form. 1. Set `web` to **Container name**. 1. Set `registry.gitlab.com//ecs-demo/master:latest` to **Image**. Alternatively, you can copy and paste the image path from the [GitLab container registry page](#push-a-containerized-application-image-to-gitlab-container-registry). @@ -123,7 +123,7 @@ An [ECS cluster](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/clu is a virtual group of [ECS services](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs_services.html). It's also associated with EC2 or Fargate as the computation resource. -1. Go to **ECS > Clusters** on [AWS console](https://aws.amazon.com/). +1. Go to **ECS** > **Clusters** on [AWS console](https://aws.amazon.com/). 1. Select **Create Cluster**. 1. Select **EC2 Linux + Networking** as the cluster template. Select **Next Step**. 1. Set `ecs-demo` to **Cluster Name**. @@ -171,7 +171,7 @@ instructions, select the closest one. Now, the demo application is accessible from the internet. -1. Go to **EC2 > Instances** on the [AWS console](https://aws.amazon.com/) +1. Go to **EC2** > **Instances** on the [AWS console](https://aws.amazon.com/) 1. Search by `ECS Instance` to find the corresponding EC2 instance that [the ECS cluster created](#create-an-ecs-cluster). 1. Select the ID of the EC2 instance. This brings you to the instance detail page. 1. Copy **Public IPv4 address** and paste it in the browser. Now you can see the demo application @@ -191,7 +191,7 @@ Now that you have an application running on ECS, you can set up continuous deplo For GitLab to access the ECS cluster, service, and task definition that you previously created, you must create a deployer user on AWS: -1. Go to **IAM > Users** on [AWS console](https://aws.amazon.com/). +1. Go to **IAM** > **Users** on [AWS console](https://aws.amazon.com/). 1. Select **Add user**. 1. Set `ecs_demo` to **User name**. 1. Enable **Programmatic access** checkbox. Select **Next: Permissions**. diff --git a/doc/ci/components/_index.md b/doc/ci/components/_index.md index 4508c3ec5e1805..7985d3827a3164 100644 --- a/doc/ci/components/_index.md +++ b/doc/ci/components/_index.md @@ -644,7 +644,7 @@ Prerequisites: To set the project as a catalog project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. Turn on the **CI/CD Catalog project** toggle. diff --git a/doc/ci/environments/_index.md b/doc/ci/environments/_index.md index b3b60cabe86f7f..a1f22f579ad7c2 100644 --- a/doc/ci/environments/_index.md +++ b/doc/ci/environments/_index.md @@ -35,7 +35,7 @@ There are a few ways to view a list of environments for a given project: - On the project's overview page, if at least one environment is available (that is, not stopped). ![A project overview page displaying the number of available environments as an incremental counter.](img/environments_project_home_v15_9.png) -- On the left sidebar, select **Operate > Environments**. +- On the left sidebar, select **Operate** > **Environments**. The environments are displayed. ![A list of available environments in a GitLab project, showing environment names, statuses, and other relevant details.](img/environments_list_v14_8.png) @@ -118,7 +118,7 @@ Prerequisites: To create a static environment in the UI: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select **Create an environment**. 1. Complete the fields. 1. Select **Save**. @@ -370,7 +370,7 @@ GitLab validates the pipeline configuration at pipeline creation. To search environments by name: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. In the search bar, enter your search term. - The length of your **search term should be 3 or more characters**. - Matching applies from the beginning of the environment name. @@ -420,7 +420,7 @@ Environments view, the stop and deploy jobs must be in the same To stop an environment in the GitLab UI: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Next to the environment you want to stop, select **Stop**. 1. On the confirmation dialog, select **Stop environment**. @@ -571,7 +571,7 @@ you can view its expiration date and time. To view an environment's expiration date and time: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select the name of the environment. The expiration date and time is displayed in the upper-left corner, next to the environment's name. @@ -584,7 +584,7 @@ you can override its expiration. To override an environment's expiration in the UI: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select the environment name. 1. in the upper-right corner, select the thumbtack ({{< icon name="thumbtack" >}}). @@ -614,7 +614,7 @@ Prerequisites: To clean up stale environments: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select **Clean up environments**. 1. Select the date to use for determining which environments to consider stale. 1. Select **Clean up**. @@ -759,7 +759,7 @@ Prerequisites: To delete an environment: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select the **Stopped** tab. 1. Next to the environment you want to delete, select **Delete environment**. 1. On the confirmation dialog, select **Delete environment**. diff --git a/doc/ci/environments/deployment_approvals.md b/doc/ci/environments/deployment_approvals.md index 8111710f8871c0..ca623628b18617 100644 --- a/doc/ci/environments/deployment_approvals.md +++ b/doc/ci/environments/deployment_approvals.md @@ -109,7 +109,7 @@ Prerequisites: To approve or reject a deployment: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select the environment's name. 1. Find the deployment and select its **Status badge**. 1. Optional. Add a comment which describes your reason for approving or rejecting the deployment. @@ -136,7 +136,7 @@ granted. To view the approval details of a deployment: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select the environment's name. 1. Find the deployment and select its **Status badge**. @@ -154,7 +154,7 @@ Review the status of your deployments, including whether a deployment is blocked To view your deployments: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select the environment being deployed to. A deployment with the **blocked** label is blocked. diff --git a/doc/ci/environments/deployments.md b/doc/ci/environments/deployments.md index b3674a13da6ea1..2fef98ddcd6f7a 100644 --- a/doc/ci/environments/deployments.md +++ b/doc/ci/environments/deployments.md @@ -134,7 +134,7 @@ If there is a problem with a deployment, you can retry it or roll it back. To retry or roll back a deployment: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select the environment. 1. To the right of the deployment name: - To retry a deployment, select **Re-deploy to environment**. diff --git a/doc/ci/environments/kubernetes_dashboard.md b/doc/ci/environments/kubernetes_dashboard.md index 2e62071cf4bb20..4bd69d0b1df436 100644 --- a/doc/ci/environments/kubernetes_dashboard.md +++ b/doc/ci/environments/kubernetes_dashboard.md @@ -52,7 +52,7 @@ Prerequisites: {{< tab title="The environment already exists" >}} 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select the environment to be associated with the agent for Kubernetes. 1. Select **Edit**. 1. Select a GitLab agent for Kubernetes. @@ -65,7 +65,7 @@ Prerequisites: {{< tab title="The environment doesn't exist" >}} 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select **New environment**. 1. Complete the **Name** field. 1. Select a GitLab agent for Kubernetes. @@ -121,7 +121,7 @@ Kubernetes resources and Flux reconciliation updates in real time. To view a configured dashboard: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select the environment associated with the agent for Kubernetes. 1. Select the **Kubernetes overview** tab. @@ -266,7 +266,7 @@ To view a detailed dashboard: 1. Find your agent for Kubernetes ID: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Operate > Kubernetes clusters**. + 1. Select **Operate** > **Kubernetes clusters**. 1. Copy the numerical ID of the agent you want to access. 1. Go to one of the following URLs, replacing `` with your agent ID: diff --git a/doc/ci/examples/semantic-release.md b/doc/ci/examples/semantic-release.md index 4ddce2b04611f4..36ae2b86af86e7 100644 --- a/doc/ci/examples/semantic-release.md +++ b/doc/ci/examples/semantic-release.md @@ -97,7 +97,7 @@ As part of publishing a package, semantic-release increases the version number i 1. Open the left sidebar. -1. Select **Settings > Access tokens**. +1. Select **Settings** > **Access tokens**. 1. In your project, select **Add new token**. 1. In the **Token name** box, enter a token name. 1. Under **Select scopes**, select the **api** checkbox. diff --git a/doc/ci/jobs/_index.md b/doc/ci/jobs/_index.md index b3274e0c82c7e6..ba91ce3338555f 100644 --- a/doc/ci/jobs/_index.md +++ b/doc/ci/jobs/_index.md @@ -230,7 +230,7 @@ Filtering jobs by name is an [experiment](../../policy/development_stages_suppor To view the full list of jobs that ran in a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Jobs**. +1. Select **Build** > **Jobs**. You can filter the list by [job name](#job-names), [job status](#available-job-statuses), and [job source](#available-job-sources). @@ -383,7 +383,7 @@ To retry a job from the job log: To retry a job from a pipeline: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. Find the pipeline that contains the job you want to retry. 1. From the pipeline graph, next to the job you want to retry, select **Run again** ({{< icon name="retry" >}}). @@ -393,7 +393,7 @@ If a pipeline has multiple failed or canceled jobs, you can retry all of them at 1. On the left sidebar, select **Search or go to** and find your project. 1. Do one of the following: - - Select **Build > Pipelines**. + - Select **Build** > **Pipelines**. - Go to a merge request and select the **Pipelines** tab. 1. For the pipeline with failed or canceled jobs, select **Retry all failed or canceled jobs** ({{< icon name="retry" >}}). @@ -455,7 +455,7 @@ To cancel a job from the job log: To cancel a job from a pipeline: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. Find the pipeline that contains the job you want to cancel. 1. From the pipeline graph, next to the job you want to cancel, select **Cancel** ({{< icon name="cancel" >}}). @@ -465,7 +465,7 @@ You can cancel all jobs in a running pipeline at once. 1. On the left sidebar, select **Search or go to** and find your project. 1. Do one of the following: - - Select **Build > Pipelines**. + - Select **Build** > **Pipelines**. - Go to a merge request and select the **Pipelines** tab. 1. For the pipeline you want to cancel, select **Cancel the running pipeline** ({{< icon name="cancel" >}}). diff --git a/doc/ci/jobs/ci_job_token.md b/doc/ci/jobs/ci_job_token.md index 4d5554a16d3c6d..9e694353ee6f72 100644 --- a/doc/ci/jobs/ci_job_token.md +++ b/doc/ci/jobs/ci_job_token.md @@ -283,7 +283,7 @@ Prerequisites: To set a feature to be only visible to project members: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. Set the visibility to **Only project members** for the features you want to restrict access to. - The ability to fetch artifacts is controlled by the CI/CD visibility setting. diff --git a/doc/ci/jobs/job_artifacts.md b/doc/ci/jobs/job_artifacts.md index 1f2becae674112..1cda52131ce7cf 100644 --- a/doc/ci/jobs/job_artifacts.md +++ b/doc/ci/jobs/job_artifacts.md @@ -201,7 +201,7 @@ job: {{< /history >}} -You can view all artifacts stored in a project from the **Build > Artifacts** page. +You can view all artifacts stored in a project from the **Build** > **Artifacts** page. This list displays all jobs and their associated artifacts. Expand an entry to access all artifacts associated with a job, including: @@ -353,7 +353,7 @@ You can also delete individual artifacts from the [**Artifacts** page](#bulk-del You can delete multiple artifacts at the same time: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Artifacts**. +1. Select **Build** > **Artifacts**. 1. Select the checkboxes next to the artifacts you want to delete. You can select up to 50 artifacts. 1. Select **Delete selected**. diff --git a/doc/ci/jobs/job_rules.md b/doc/ci/jobs/job_rules.md index c8e8b85319ad0b..4798294224b05d 100644 --- a/doc/ci/jobs/job_rules.md +++ b/doc/ci/jobs/job_rules.md @@ -229,7 +229,7 @@ Use the `CI_PIPELINE_SOURCE` variable to control when to add jobs for these pipe | `schedule` | For [scheduled pipelines](../pipelines/schedules.md). | | `security_orchestration_policy` | For [scheduled scan execution policies](../../user/application_security/policies/scan_execution_policies.md) pipelines. | | `trigger` | For pipelines created by using a [trigger token](../triggers/_index.md#configure-cicd-jobs-to-run-in-triggered-pipelines). | -| `web` | For pipelines created by selecting **New pipeline** in the GitLab UI, from the project's **Build > Pipelines** section. | +| `web` | For pipelines created by selecting **New pipeline** in the GitLab UI, from the project's **Build** > **Pipelines** section. | | `webide` | For pipelines created by using the [Web IDE](../../user/project/web_ide/_index.md). | These values are the same as returned for the `source` parameter when using the diff --git a/doc/ci/mobile_devops/mobile_devops_tutorial_android.md b/doc/ci/mobile_devops/mobile_devops_tutorial_android.md index 9e105861f94c77..c0d7b6d5d33d3e 100644 --- a/doc/ci/mobile_devops/mobile_devops_tutorial_android.md +++ b/doc/ci/mobile_devops/mobile_devops_tutorial_android.md @@ -131,7 +131,7 @@ Signed builds can be uploaded to the Google Play Store by using the Mobile DevOp 1. [Create a Google service account](https://docs.fastlane.tools/actions/supply/#setup) in Google Cloud Platform and grant that account access to the project in Google Play. 1. Enable the Google Play integration: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Settings > Integrations**. + 1. Select **Settings** > **Integrations**. 1. Select **Google Play**. 1. Under **Enable integration**, select the **Active** checkbox. 1. In **Package name**, enter the package name of the app. For example, `com.gitlab.app_name`. diff --git a/doc/ci/mobile_devops/mobile_devops_tutorial_ios.md b/doc/ci/mobile_devops/mobile_devops_tutorial_ios.md index 84e7a3e49366da..35bcd31eef33e7 100644 --- a/doc/ci/mobile_devops/mobile_devops_tutorial_ios.md +++ b/doc/ci/mobile_devops/mobile_devops_tutorial_ios.md @@ -123,7 +123,7 @@ To create an iOS distribution with the Apple Store integration and fastlane: 1. Generate an API Key for App Store Connect API. In the Apple App Store Connect portal, [generate a new private key for your project](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api). 1. Enable the Apple App Store Connect integration: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Settings > Integrations**. + 1. Select **Settings** > **Integrations**. 1. Select **Apple App Store Connect**. 1. Under **Enable integration**, select the **Active** checkbox. 1. Provide the Apple App Store Connect configuration information: diff --git a/doc/ci/pipeline_editor/_index.md b/doc/ci/pipeline_editor/_index.md index cd39e4dda37ccf..f0c9909ff85707 100644 --- a/doc/ci/pipeline_editor/_index.md +++ b/doc/ci/pipeline_editor/_index.md @@ -13,7 +13,7 @@ title: Pipeline editor {{< /details >}} The pipeline editor is the primary place to edit the GitLab CI/CD configuration in -the `.gitlab-ci.yml` file in the root of your repository. To access the editor, go to **Build > Pipeline editor**. +the `.gitlab-ci.yml` file in the root of your repository. To access the editor, go to **Build** > **Pipeline editor**. From the pipeline editor page you can: @@ -48,7 +48,7 @@ To test the validity of your GitLab CI/CD configuration before committing the ch you can use the CI lint tool: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline editor**. +1. Select **Build** > **Pipeline editor**. 1. Select the **Validate** tab. This tool checks for syntax and logical errors but goes into more detail than the @@ -87,7 +87,7 @@ for review. ## Visualize CI configuration To view a visualization of your `.gitlab-ci.yml` configuration, in your project, -go to **Build > Pipeline editor**, and then select the **Visualize** tab. The +go to **Build** > **Pipeline editor**, and then select the **Visualize** tab. The visualization shows all stages and jobs. Any [`needs`](../yaml/_index.md#needs) relationships are displayed as lines connecting jobs together, showing the hierarchy of execution. diff --git a/doc/ci/pipelines/_index.md b/doc/ci/pipelines/_index.md index 186e20d009c107..f6d6f8fe5dad64 100644 --- a/doc/ci/pipelines/_index.md +++ b/doc/ci/pipelines/_index.md @@ -96,7 +96,7 @@ operation of the pipeline. To execute a pipeline manually: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. Select **New pipeline**. 1. In the **Run for branch name or tag** field, select the branch or tag to run the pipeline for. 1. (Optional) Enter any: @@ -251,7 +251,7 @@ The `ci.skip` push option does not skip merge request pipelines. Users with the Owner role for a project can delete a pipeline: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. Select either the pipeline ID (for example `#123456789`) or the pipeline status icon (for example **Passed**) of the pipeline to delete. 1. In the top right of the pipeline details page, select **Delete**. @@ -391,7 +391,7 @@ running time is: To view all the pipelines that ran for your project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. You can filter the **Pipelines** page by: diff --git a/doc/ci/pipelines/dedicated_hosted_runner_compute_minutes.md b/doc/ci/pipelines/dedicated_hosted_runner_compute_minutes.md index 7a4e48fbcb99ab..147bbad323340e 100644 --- a/doc/ci/pipelines/dedicated_hosted_runner_compute_minutes.md +++ b/doc/ci/pipelines/dedicated_hosted_runner_compute_minutes.md @@ -46,4 +46,4 @@ You can see compute usage: To view GitLab-hosted runner compute usage for all namespaces across your entire GitLab instance: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Usage Quotas**. +1. Select **Settings** > **Usage Quotas**. diff --git a/doc/ci/pipelines/instance_runner_compute_minutes.md b/doc/ci/pipelines/instance_runner_compute_minutes.md index 042e657beb13dd..e61e8a8b8d799f 100644 --- a/doc/ci/pipelines/instance_runner_compute_minutes.md +++ b/doc/ci/pipelines/instance_runner_compute_minutes.md @@ -81,7 +81,7 @@ To view compute usage for your group: 1. On the left sidebar, select **Search or go to** and find your group. The group must not be a subgroup. -1. Select **Settings > Usage Quotas**. +1. Select **Settings** > **Usage Quotas**. 1. Select the **Pipelines** tab. The projects list shows projects with compute usage or instance runners usage diff --git a/doc/ci/pipelines/merge_trains.md b/doc/ci/pipelines/merge_trains.md index 130ee137cb7a81..a0ae988cb08a62 100644 --- a/doc/ci/pipelines/merge_trains.md +++ b/doc/ci/pipelines/merge_trains.md @@ -113,7 +113,7 @@ Prerequisites: To enable merge trains: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Merge requests**. +1. Select **Settings** > **Merge requests**. 1. In GitLab 16.4 and earlier, in the **Merge method** section, verify that **Merge commit** is selected. In GitLab 16.5 and later, you can use any merge method. 1. In the **Merge options** section, ensure **Enable merged results pipelines** is enabled @@ -153,7 +153,7 @@ The merge train details page shows active merge requests in the queue and merged To access the merge train details from the list of merge requests: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Merge requests**. +1. Select **Code** > **Merge requests**. 1. Above the list of merge requests, select **Merge trains**. 1. Optional. Filter the merge trains by target branch. @@ -284,7 +284,7 @@ Prerequisites: To enable skipping the train without pipeline restarts: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Merge requests**. +1. Select **Settings** > **Merge requests**. 1. In the **Merge options** section, ensure the **Enable merged results pipelines** and **Enable merge trains** options are enabled. 1. Select **Allow skipping the merge train**. diff --git a/doc/ci/pipelines/merged_results_pipelines.md b/doc/ci/pipelines/merged_results_pipelines.md index 79e92337e961eb..f3441546cea396 100644 --- a/doc/ci/pipelines/merged_results_pipelines.md +++ b/doc/ci/pipelines/merged_results_pipelines.md @@ -43,7 +43,7 @@ To enable merged results pipelines in a project, you must have at least the Maintainer role: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Merge requests**. +1. Select **Settings** > **Merge requests**. 1. In the **Merge options** section, select **Enable merged results pipelines**. 1. Select **Save changes**. diff --git a/doc/ci/pipelines/schedules.md b/doc/ci/pipelines/schedules.md index d3d0afc5d663d8..45ea0984abb42b 100644 --- a/doc/ci/pipelines/schedules.md +++ b/doc/ci/pipelines/schedules.md @@ -36,7 +36,7 @@ Otherwise, the pipeline is not created. No error message is displayed. To add a pipeline schedule: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline schedules**. +1. Select **Build** > **Pipeline schedules**. 1. Select **New schedule** and fill in the form. - **Interval Pattern**: Select one of the preconfigured intervals, or enter a custom interval in [cron notation](../../topics/cron/_index.md). You can use any cron value, @@ -58,7 +58,7 @@ you must delete unused schedules before you can add another. The owner of a pipeline schedule can edit it: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline schedules**. +1. Select **Build** > **Pipeline schedules**. 1. Next to the schedule, select **Edit** ({{< icon name="pencil" >}}) and fill in the form. The user must have at least the Developer role for the project. If the user is @@ -71,7 +71,7 @@ To trigger a pipeline schedule manually, so that it runs immediately instead of the next scheduled time: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline schedules**. +1. Select **Build** > **Pipeline schedules**. 1. On the right of the list, for the pipeline you want to run, select **Run** ({{< icon name="play" >}}). @@ -90,7 +90,7 @@ including [protected environments](../environments/protected_environments.md) an To take ownership of a pipeline created by a different user: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline schedules**. +1. Select **Build** > **Pipeline schedules**. 1. On the right of the list, for the pipeline you want to become owner of, select **Take ownership**. diff --git a/doc/ci/pipelines/settings.md b/doc/ci/pipelines/settings.md index 501cda0a0d769a..3275e6ce567d57 100644 --- a/doc/ci/pipelines/settings.md +++ b/doc/ci/pipelines/settings.md @@ -62,7 +62,7 @@ This setting has no effect when: To change the pipeline visibility for non-project members: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. For **CI/CD**, choose: - **Only project members**: Only project members can view pipelines. @@ -263,7 +263,7 @@ When you disable GitLab CI/CD: To disable GitLab CI/CD in your project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. In the **Repository** section, turn off **CI/CD**. 1. Select **Save changes**. diff --git a/doc/ci/quick_start/_index.md b/doc/ci/quick_start/_index.md index 4f7de113cdf0fc..4c9286e369752f 100644 --- a/doc/ci/quick_start/_index.md +++ b/doc/ci/quick_start/_index.md @@ -80,7 +80,7 @@ In this file, you define: To create a `.gitlab-ci.yml` file in your project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Repository**. +1. Select **Code** > **Repository**. 1. Above the file list, select the branch you want to commit to. If you're not sure, leave `master` or `main`. Then select the plus icon ({{< icon name="plus" >}}) and **New file**: @@ -129,7 +129,7 @@ The pipeline starts and runs the jobs you defined in the `.gitlab-ci.yml` file. Now take a look at your pipeline and the jobs within. -1. Go to **Build > Pipelines**. A pipeline with three stages should be displayed: +1. Go to **Build** > **Pipelines**. A pipeline with three stages should be displayed: ![The pipeline list shows a running pipeline with 3 stages](img/three_stages_v13_6.png) diff --git a/doc/ci/quick_start/tutorial.md b/doc/ci/quick_start/tutorial.md index f68ce9cd90952e..8b2053cca475d7 100644 --- a/doc/ci/quick_start/tutorial.md +++ b/doc/ci/quick_start/tutorial.md @@ -117,7 +117,7 @@ test-job: Commit and push this change to GitLab, then: -1. Go to **Build > Pipelines** and make sure a pipeline runs in GitLab with this single job. +1. Go to **Build** > **Pipelines** and make sure a pipeline runs in GitLab with this single job. 1. Select the pipeline, then select the job to view the job's log and see the `This is my first job!` message followed by the date. @@ -224,7 +224,7 @@ and view the pipeline details from the **Pipelines** list. Verify that: To view your site: -- On the left sidebar, select **Deploy > Pages**. +- On the left sidebar, select **Deploy** > **Pages**. - Make sure **Use unique domain** is off. - Under **Access pages**, select the link. The URL format should be similar to: `https://.gitlab.io/`. For more information, see [GitLab Pages default domain names](../../user/project/pages/getting_started_part_one.md#gitlab-pages-default-domain-names). diff --git a/doc/ci/review_apps/_index.md b/doc/ci/review_apps/_index.md index 77c91027dd8f2f..2d2431820dba19 100644 --- a/doc/ci/review_apps/_index.md +++ b/doc/ci/review_apps/_index.md @@ -101,7 +101,7 @@ Prerequisites: To configure review apps in your project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline editor**. +1. Select **Build** > **Pipeline editor**. 1. In your `.gitlab-ci.yml` file, add a job that creates a [dynamic environment](../environments/_index.md#create-a-dynamic-environment). You can use a [predefined CI/CD variable](../variables/predefined_variables.md) to differentiate each environment. For example, using the `CI_COMMIT_REF_SLUG` predefined variable: @@ -130,7 +130,7 @@ GitLab provides a built-in template that's configured for merge request pipeline To use and customize this template: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select **Enable review apps**. 1. From the **Enable Review Apps** dialog that appears, copy the YAML template: @@ -146,7 +146,7 @@ To use and customize this template: - if: $CI_PIPELINE_SOURCE == "merge_request_event" ``` -1. Select **Build > Pipeline editor**. +1. Select **Build** > **Pipeline editor**. 1. Paste the template into your `.gitlab-ci.yml` file. 1. Customize the template based on your deployment needs: @@ -357,7 +357,7 @@ To view a mapped page from a file: To view mapped pages from a commit: 1. Go to a commit that has a review app deployment: - - For branch pipelines: Select **Code > Commits** and select a commit with a pipeline badge. + - For branch pipelines: Select **Code** > **Commits** and select a commit with a pipeline badge. - For merge request pipelines: In your merge request, select the **Commits** tab and select a commit. - For merged results pipelines: In your merge request, select the **Pipelines** tab and select the pipeline commit. 1. Select the review app icon ({{< icon name="external-link" >}}) next to a filename that matches your route map. diff --git a/doc/ci/runners/configure_runners.md b/doc/ci/runners/configure_runners.md index 9b5dc3ac183207..92c7ac7e185e99 100644 --- a/doc/ci/runners/configure_runners.md +++ b/doc/ci/runners/configure_runners.md @@ -53,7 +53,7 @@ Prerequisites: To set the maximum job timeout: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Build > Runners**. +1. Select **Build** > **Runners**. 1. To the right of the runner you want to edit, select **Edit** ({{< icon name="pencil" >}}). 1. In the **Maximum job timeout** field, enter a value in seconds. The minimum value is 600 seconds (10 minutes). 1. Select **Save changes**. @@ -312,7 +312,7 @@ Prerequisites: - You must have the Owner role for the group. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Build > Runners**. +1. Select **Build** > **Runners**. 1. To the right of the runner you want to protect, select **Edit** ({{< icon name="pencil" >}}). 1. Select the **Protected** checkbox. 1. Select **Save changes**. @@ -364,7 +364,7 @@ Prerequisites: To control the jobs that a group runner can run: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Build > Runners**. +1. Select **Build** > **Runners**. 1. To the right of the runner you want to edit, select **Edit** ({{< icon name="pencil" >}}). 1. Set the runner to run tagged or untagged jobs: - To run tagged jobs, in the **Tags** field, enter the job tags separated with a comma. For example, `macos`, `ruby`. diff --git a/doc/ci/runners/runner_fleet_dashboard_groups.md b/doc/ci/runners/runner_fleet_dashboard_groups.md index c43e0372d331ae..c7fda0d05589c6 100644 --- a/doc/ci/runners/runner_fleet_dashboard_groups.md +++ b/doc/ci/runners/runner_fleet_dashboard_groups.md @@ -45,7 +45,7 @@ Prerequisites: To view the runner fleet dashboard for groups: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Build > Runners**. +1. Select **Build** > **Runners**. 1. Select **Fleet dashboard**. For GitLab Self-Managed, most of the dashboard metrics work without any additional configuration. diff --git a/doc/ci/runners/runners_scope.md b/doc/ci/runners/runners_scope.md index 371a80dd4377e7..4e8ed816f247b1 100644 --- a/doc/ci/runners/runners_scope.md +++ b/doc/ci/runners/runners_scope.md @@ -268,7 +268,7 @@ The runner uses the token to authenticate with GitLab when it picks up jobs from To create a group runner: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Build > Runners**. +1. Select **Build** > **Runners**. 1. Select **New group runner**. 1. In the **Tags** section, in the **Tags** field, enter the job tags to specify jobs the runner can run. If there are no job tags for this runner, select **Run untagged**. @@ -322,7 +322,7 @@ To create a group runner: 1. [Install GitLab Runner](https://docs.gitlab.com/runner/install/). 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Build > Runners**. +1. Select **Build** > **Runners**. 1. In the upper-right corner, select **Register a group runner**. 1. Select **Show runner installation and registration instructions**. These instructions include the token, URL, and a command to register a runner. @@ -346,7 +346,7 @@ You can view all runners for a group and its subgroups and projects. You can do this for GitLab Self-Managed or for GitLab.com. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Build > Runners**. +1. Select **Build** > **Runners**. #### Filter group runners to show only inherited @@ -366,7 +366,7 @@ To show all runners available in the instance, including instance runners and those in other groups: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Build > Runners**. +1. Select **Build** > **Runners**. 1. Above the list, turn off the **Show only inherited** toggle. ### Pause or resume a group runner @@ -379,7 +379,7 @@ You can pause a runner so that it does not accept jobs from subgroups and projec instance. If you pause a group runner that is used by multiple projects, the runner pauses for all projects. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Build > Runners**. +1. Select **Build** > **Runners**. 1. In the search box, enter the runner description or filter the runner list. 1. In the runner list, to the right of the runner: - To pause the runner, select **Pause** ({{< icon name="pause" >}}). @@ -404,7 +404,7 @@ jobs, you can [pause](#pause-or-resume-a-group-runner) the runner instead. To delete a single or multiple group runners: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Build > Runners**. +1. Select **Build** > **Runners**. 1. In the search box, enter the runner description or filter the list of runners. 1. Delete the group runner: - To delete a single runner, next to the runner, select **Delete runner** ({{< icon name="remove" >}}). @@ -734,7 +734,7 @@ To determine which runners need to be upgraded: 1. View the list of runners: - For a group: 1. On the left sidebar, select **Search or go to** and find your group. - 1. Select **Build > Runners**. + 1. Select **Build** > **Runners**. - For the instance: 1. On the left sidebar, at the bottom, select **Admin**. 1. Select **CI/CD > Runners**. diff --git a/doc/ci/secrets/fortanix_dsm_integration.md b/doc/ci/secrets/fortanix_dsm_integration.md index 3a6df5a3383c05..9cd0c12c7654ba 100644 --- a/doc/ci/secrets/fortanix_dsm_integration.md +++ b/doc/ci/secrets/fortanix_dsm_integration.md @@ -135,7 +135,7 @@ To generate a new secret in Fortanix DSM and use it with GitLab: 1. The pipeline should run automatically after saving the `.gitlab-ci.yml` file. If not, select **Build > Pipelines > Run pipeline**. -1. Go to **Build > Jobs** and check the `build` job's log: +1. Go to **Build** > **Jobs** and check the `build` job's log: ![gitlab_build_result_1](img/gitlab_build_result_1_v16_9.png) @@ -176,7 +176,7 @@ To use a secret that already exists in Fortanix DSM with GitLab: 1. The pipeline should run automatically after saving the `.gitlab-ci.yml` file. If not, select **Build > Pipelines > Run pipeline**. -1. Go to **Build > Jobs** and check the `build` job's log: +1. Go to **Build** > **Jobs** and check the `build` job's log: - ![gitlab_build_result_2](img/gitlab_build_result_2_v16_9.png) @@ -226,6 +226,6 @@ To set up code signing securely in your GitLab environment: 1. The pipeline should run automatically after saving the `.gitlab-ci.yml` file. If not, select **Build > Pipelines > Run pipeline**. -1. Go to **Build > Jobs** and check the `build` job's log: +1. Go to **Build** > **Jobs** and check the `build` job's log: - ![gitlab_build_result_3](img/gitlab_build_result_3_v16_9.png) diff --git a/doc/ci/secrets/gcp_secret_manager.md b/doc/ci/secrets/gcp_secret_manager.md index 2a38ce81a01363..dddd78c432d2aa 100644 --- a/doc/ci/secrets/gcp_secret_manager.md +++ b/doc/ci/secrets/gcp_secret_manager.md @@ -62,7 +62,7 @@ The principal is used to authorize access to the Secret Manager resources: After setting up WIF, you must grant the WIF principal access to the secrets in Secret Manager. -1. In GCP Console, go to **Security > Secret Manager**. +1. In GCP Console, go to **Security** > **Secret Manager**. 1. Select the name of the secret you wish to grant access to, to view the secret's details. 1. From the **PERMISSIONS** tab, select **GRANT ACCESS** to grant access to the principal set created through the WIF provider. The external identity format is: diff --git a/doc/ci/test_cases/_index.md b/doc/ci/test_cases/_index.md index d25355e01960bf..7f350366fca288 100644 --- a/doc/ci/test_cases/_index.md +++ b/doc/ci/test_cases/_index.md @@ -46,7 +46,7 @@ Prerequisites: To create a test case in a GitLab project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Test cases**. +1. Select **Build** > **Test cases**. 1. Select **New test case**. You are taken to the new test case form. Here you can enter the new case's title, [description](../../user/markdown.md), attach a file, and assign [labels](../../user/project/labels.md). 1. Select **Submit test case**. You are taken to view the new test case. @@ -65,7 +65,7 @@ Prerequisites: To view a test case: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Test cases**. +1. Select **Build** > **Test cases**. 1. Select the title of the test case you want to view. You are taken to the test case page. ![An example test case page](img/test_case_show_v13_10.png) @@ -135,7 +135,7 @@ To archive a test case, on the test case's page, select **Archive test case**. To view archived test cases: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Test cases**. +1. Select **Build** > **Test cases**. 1. Select **Archived**. ## Reopen an archived test case diff --git a/doc/ci/testing/code_coverage/_index.md b/doc/ci/testing/code_coverage/_index.md index 288850f4f916b1..9853db5ff5cc90 100644 --- a/doc/ci/testing/code_coverage/_index.md +++ b/doc/ci/testing/code_coverage/_index.md @@ -207,7 +207,7 @@ Prerequisites: To add a `Coverage-Check` approval rule: -1. Go to your project and select **Settings > Merge requests**. +1. Go to your project and select **Settings** > **Merge requests**. 1. Under **Merge request approvals**, do one of the following: - Next to the `Coverage-Check` approval rule, select **Enable**. - For manual setup, select **Add approval rule**, then enter `Coverage-Check` as the **Rule name**. @@ -236,7 +236,7 @@ You can track the evolution of code coverage for your project or group over time To view the code coverage history for a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Analyze > Repository analytics**. +1. Select **Analyze** > **Repository analytics**. 1. From the dropdown list, select the job you want to view historical data for. 1. Optional. To view a CSV file of the data, select **Download raw data (.csv)**. @@ -251,7 +251,7 @@ To view the code coverage history for a project: To view the code coverage history for all projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Analyze > Repository analytics**. +1. Select **Analyze** > **Repository analytics**. 1. Optional. To view a CSV file of the data, select **Download historic test coverage data (.csv)**. ## Display coverage badges diff --git a/doc/ci/triggers/_index.md b/doc/ci/triggers/_index.md index ad61ed84ea5385..5dde20ab9756a7 100644 --- a/doc/ci/triggers/_index.md +++ b/doc/ci/triggers/_index.md @@ -230,7 +230,7 @@ You can see which pipeline trigger token caused a job to run by visiting the sin A part of the trigger token displays on the right sidebar, under **Job details**. In pipelines triggered with a trigger token, jobs are labeled as `triggered` in -**Build > Jobs**. +**Build** > **Jobs**. ## Troubleshooting diff --git a/doc/ci/yaml/_index.md b/doc/ci/yaml/_index.md index 669ea58e189c76..36e19414773dd1 100644 --- a/doc/ci/yaml/_index.md +++ b/doc/ci/yaml/_index.md @@ -4048,7 +4048,7 @@ release_job: This example creates a release: - When you push a Git tag. -- When you add a Git tag in the UI at **Code > Tags**. +- When you add a Git tag in the UI at **Code** > **Tags**. **Additional details**: diff --git a/doc/ci/yaml/deprecated_keywords.md b/doc/ci/yaml/deprecated_keywords.md index 4f33d4798be05c..8e414b3e1bb871 100644 --- a/doc/ci/yaml/deprecated_keywords.md +++ b/doc/ci/yaml/deprecated_keywords.md @@ -81,7 +81,7 @@ pipeline based on branch names or pipeline types. | `schedules` | For [scheduled pipelines](../pipelines/schedules.md). | | `tags` | When the Git reference for a pipeline is a tag. | | `triggers` | For pipelines created by using a [trigger token](../triggers/_index.md#configure-cicd-jobs-to-run-in-triggered-pipelines). | - | `web` | For pipelines created by selecting **New pipeline** in the GitLab UI, from the project's **Build > Pipelines** section. | + | `web` | For pipelines created by selecting **New pipeline** in the GitLab UI, from the project's **Build** > **Pipelines** section. | **Example of `only:refs` and `except:refs`**: diff --git a/doc/ci/yaml/lint.md b/doc/ci/yaml/lint.md index 32bf2f01f4eea2..54a2c212187e0b 100644 --- a/doc/ci/yaml/lint.md +++ b/doc/ci/yaml/lint.md @@ -31,7 +31,7 @@ configuration added with the [`includes` keyword](_index.md#include). To check CI/CD configuration with the CI lint tool: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline editor**. +1. Select **Build** > **Pipeline editor**. 1. Select the **Validate** tab. 1. Select **Lint CI/CD sample**. 1. Paste a copy of the CI/CD configuration you want to check into the text box. @@ -51,7 +51,7 @@ Prerequisites: To simulate a pipeline: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline editor**. +1. Select **Build** > **Pipeline editor**. 1. Select the **Validate** tab. 1. Select **Lint CI/CD sample**. 1. Paste a copy of the CI/CD configuration you want to check into the text box. diff --git a/doc/development/ai_features/ai_development_license.md b/doc/development/ai_features/ai_development_license.md index e299f36da827e4..507a8bf505232f 100644 --- a/doc/development/ai_features/ai_development_license.md +++ b/doc/development/ai_features/ai_development_license.md @@ -47,7 +47,7 @@ Developers may also choose to connect their local GitLab instance to the staging To connect to the staging AI Gateway, configure it through the Admin UI. This option is only available with Ultimate license and active Duo Enterprise add-on: -1. Go to **Admin Area** > **Settings** > **GitLab Duo** > **Self-hosted models** +1. Go to **Admin Area**** > ****Settings**** > ****GitLab Duo**** > ****Self-hosted models** 1. Set the **AI Gateway URL** to `https://cloud.staging.gitlab.com/ai` 1. Select **Save changes** @@ -58,7 +58,7 @@ Ai::Setting.instance.update!(ai_gateway_url: 'https://cloud.staging.gitlab.com/a ``` - Restart your GDK. -- Inside your GDK, navigate to **Admin area** > **GitLab Duo Pro**, navigate to `/admin/code_suggestions` +- Inside your GDK, navigate to **Admin area**** > ****GitLab Duo Pro**, navigate to `/admin/code_suggestions` - Filter users to find `root` and use the toggle to assign a GitLab Duo Pro add-on seat to the root user. ## Troubleshooting @@ -95,7 +95,7 @@ When working in staging environments, you may need to set up Duo add-ons for you 1. Have your account ready at . 1. [Create a new group](../../user/group/_index.md#create-a-group) or use an existing one as the namespace which will receive the Duo Pro access. -1. Go to **Settings > Billing**. +1. Go to **Settings** > **Billing**. 1. Initiate the purchase flow for the Ultimate plan by clicking on `Upgrade to Ultimate`. 1. After being redirected to , click on `Continue with your Gitlab.com account`. 1. Purchase the SaaS Ultimate subscription using [a test credit card](https://gitlab.com/gitlab-org/customers-gitlab-com#testing-credit-card-information). diff --git a/doc/development/ai_features/amazon_q_integration.md b/doc/development/ai_features/amazon_q_integration.md index 0022210c0b415d..f3e922649169b9 100644 --- a/doc/development/ai_features/amazon_q_integration.md +++ b/doc/development/ai_features/amazon_q_integration.md @@ -50,7 +50,7 @@ This guide describes how to set up Amazon Q in a GitLab Linux package running in 1. Go to [staging customers portal](https://customers.staging.gitlab.com/), select "Signin with GitLab.com account". 1. Instead of clicking "Buy new subscription", go to the [product page](https://customers.staging.gitlab.com/subscriptions/new?plan_id=2c92a00c76f0c6c20176f2f9328b33c9) directly. For reason of this, see [buy_subscription](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/8aa922840091ad5c5d96ada43d0065a1b6198841/doc/flows/buy_subscription.md) 1. Purchase the subscription using [a test credit card](https://gitlab.com/gitlab-org/customers-gitlab-com/#testing-credit-card-information). An activation code will be given. Do not purchase a duo-pro add-on, because currently duo-pro and Q are mutually exclusive. - 1. Go to the GitLab instance created earlier (`https://.nip.io`), log in with root account. Then on the left sidebar, go to **Admin > Subscription**, and enter the activation code + 1. Go to the GitLab instance created earlier (`https://.nip.io`), log in with root account. Then on the left sidebar, go to **Admin** > **Subscription**, and enter the activation code ## Create and configure an AWS sandbox diff --git a/doc/development/cicd/schema.md b/doc/development/cicd/schema.md index 50f9db5eca1313..b26f98607b6e90 100644 --- a/doc/development/cicd/schema.md +++ b/doc/development/cicd/schema.md @@ -135,7 +135,7 @@ under the topmost **properties** key. ### Verify changes -1. Go to **CI/CD** > **Editor**. +1. Go to **CI/CD**** > ****Editor**. 1. Write your CI/CD configuration in the editor and verify that the schema validates it correctly. diff --git a/doc/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md b/doc/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md index 532e58a711bcce..99b290959cd89b 100644 --- a/doc/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md +++ b/doc/development/contributing/first_contribution/configure-dev-env-gdk-in-a-box.md @@ -62,7 +62,7 @@ You might need to modify the system configuration of your container runtime (CPU {{< /alert >}} 1. Start the container. -1. In VS Code, select **Terminal > New terminal**, then run a `curl` command to add an SSH key to your local `~/.ssh/config`: +1. In VS Code, select **Terminal** > **New terminal**, then run a `curl` command to add an SSH key to your local `~/.ssh/config`: ```shell curl "https://gitlab.com/gitlab-org/gitlab-development-kit/-/raw/main/support/gdk-in-a-box/setup-ssh-key" | bash @@ -92,7 +92,7 @@ You might need to modify the system configuration of your container runtime (CPU To learn more about the script, you can examine the [`first_time_setup` code](https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/support/gdk-in-a-box/first_time_setup). -1. In VS Code, select **File > Open folder**, and go to: `/home/gdk/gitlab-development-kit/gitlab/`. +1. In VS Code, select **File** > **Open folder**, and go to: `/home/gdk/gitlab-development-kit/gitlab/`. 1. Open GitLab in your browser: `http://gdk.local:3000`. 1. Sign in with the username `root` and password `5iveL!fe`. 1. Continue to [change the code with the GDK](contribute-gdk.md). @@ -156,7 +156,7 @@ You might need to modify the system configuration (CPU cores and RAM) before sta {{< /alert >}} 1. Start the VM (you can minimize UTM or VirtualBox). -1. In VS Code, select **Terminal > New terminal**, then run a `curl` command to add an SSH key to your local `~/.ssh/config`: +1. In VS Code, select **Terminal** > **New terminal**, then run a `curl` command to add an SSH key to your local `~/.ssh/config`: ```shell curl "https://gitlab.com/gitlab-org/gitlab-development-kit/-/raw/main/support/gdk-in-a-box/setup-ssh-key" | bash @@ -188,7 +188,7 @@ You might need to modify the system configuration (CPU cores and RAM) before sta To learn more about the script, you can examine the [`first_time_setup` code](https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/support/gdk-in-a-box/first_time_setup). -1. In VS Code, select **File > Open folder**, and go to: `/home/debian/gitlab-development-kit/gitlab/`. +1. In VS Code, select **File** > **Open folder**, and go to: `/home/debian/gitlab-development-kit/gitlab/`. 1. Open GitLab in your browser: `http://gdk.local:3000`. 1. Sign in with the username `root` and password `5iveL!fe`. 1. Continue to [change the code with the GDK](contribute-gdk.md). diff --git a/doc/development/contributing/first_contribution/contribute-web-ide.md b/doc/development/contributing/first_contribution/contribute-web-ide.md index 072738e4225a99..6838a7a6df11eb 100644 --- a/doc/development/contributing/first_contribution/contribute-web-ide.md +++ b/doc/development/contributing/first_contribution/contribute-web-ide.md @@ -29,7 +29,7 @@ to GitLab code using the Web IDE. [from the results](https://gitlab.com/search?search=%22Syntax+highlighting+theme%22&nav_source=navbar&project_id=41372369&group_id=60717473&search_code=true). In this case, `app/views/profiles/preferences/show.html.haml`. -1. Open the file in Web IDE. Select **Edit > Open in Web IDE**. +1. Open the file in Web IDE. Select **Edit** > **Open in Web IDE**. - Keyboard shortcut: . diff --git a/doc/development/documentation/_index.md b/doc/development/documentation/_index.md index 6f12b19de4fa10..8bfa825b5a02a6 100644 --- a/doc/development/documentation/_index.md +++ b/doc/development/documentation/_index.md @@ -27,7 +27,7 @@ To update the documentation: 1. Find the documentation page you want to update. If you're not sure where the page is, look at the URL of the page on . The path is listed there. -1. In the upper right, select **Edit > Edit single file**. +1. In the upper right, select **Edit** > **Edit single file**. 1. Make your updates. 1. When you're done, in the **Commit message** text box, enter a commit message. Use 3-5 words, start the first word with a capital letter, and do not end the phrase with a period. @@ -95,7 +95,7 @@ rather than using the GitLab community fork. 1. On , scroll to the bottom of the page you want to edit. 1. Select **View page source**. -1. In the upper-right corner, select **Edit > Edit single file**. +1. In the upper-right corner, select **Edit** > **Edit single file**. 1. Make your updates. 1. When you're done, in the **Commit message** text box, enter a commit message. Use 3-5 words, start the first word with a capital letter, and do not end the phrase with a period. @@ -107,7 +107,7 @@ The changes were added to GitLab in your forked repository, in a branch with the Now, create a merge request. This merge request is how the changes from your branch are merged into the GitLab `master` branch. -1. On the left sidebar, select **Code > Merge requests**. +1. On the left sidebar, select **Code** > **Merge requests**. 1. Select **New merge request**. 1. For the source branch, select your fork and branch. 1. For the target branch, select the [GitLab repository](https://gitlab.com/gitlab-org/gitlab) `master` branch. diff --git a/doc/development/documentation/styleguide/_index.md b/doc/development/documentation/styleguide/_index.md index 831d3c7fc0f1bc..75b16f2994ffd3 100644 --- a/doc/development/documentation/styleguide/_index.md +++ b/doc/development/documentation/styleguide/_index.md @@ -543,7 +543,7 @@ Include punctuation in the bold tag when it's part of the UI element itself. For example: - `**Start a review**: This a description of the button that starts a review.` -- `Select **Overview** > **Users**.` +- `Select **Overview**** > ****Users**.` ### Inline code @@ -792,7 +792,7 @@ To turn on the setting: - In the UI: - 1. In the VS Code menu, go to **Code** > **Settings** > **Settings**. + 1. In the VS Code menu, go to **Code**** > ****Settings**** > ****Settings**. 1. Search for `Limit Last Column Length`. 1. In the **Limit Last Column Length** dropdown list, select **Follow header row length**. @@ -1150,7 +1150,7 @@ To open project settings: ```markdown 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings** > **CI/CD**. +1. Select **Settings**** > ****CI/CD**. 1. Expand **General pipelines**. ``` @@ -1158,7 +1158,7 @@ To open group settings: ```markdown 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings** > **CI/CD**. +1. Select **Settings**** > ****CI/CD**. 1. Expand **General pipelines**. ``` @@ -1167,7 +1167,7 @@ To open settings for a top-level group: ```markdown 1. On the left sidebar, select **Search or go to** and find your group. This group must be at the top level. -1. Select **Settings** > **CI/CD**. +1. Select **Settings**** > ****CI/CD**. 1. Expand **General pipelines**. ``` @@ -1175,7 +1175,7 @@ To open either project or group settings: ```markdown 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Settings** > **CI/CD**. +1. Select **Settings**** > ****CI/CD**. 1. Expand **General pipelines**. ``` @@ -1195,7 +1195,7 @@ To open the **Admin** area: ```markdown 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **CI/CD**. +1. Select **Settings**** > ****CI/CD**. ``` You do not have to repeat `On the left sidebar` in your second step. diff --git a/doc/development/documentation/styleguide/word_list.md b/doc/development/documentation/styleguide/word_list.md index 9c678e824ecc92..59799e58fc1fe7 100644 --- a/doc/development/documentation/styleguide/word_list.md +++ b/doc/development/documentation/styleguide/word_list.md @@ -1044,7 +1044,7 @@ However, you can make an exception when you are writing a task and you want to r of the fields at once. For example: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings** > **CI/CD**. +1. Select **Settings**** > ****CI/CD**. 1. Expand **General pipelines**. 1. Complete the fields. @@ -1860,7 +1860,7 @@ For more information, see the When documenting high-level UI elements, use **on** as a preposition. For example: -- On the left sidebar, select **Settings** > **CI/CD**. +- On the left sidebar, select **Settings**** > ****CI/CD**. - On the **Grant permission** dialog, select **Group**. Do not use **from** or **in**. For more information, see the [Microsoft Style Guide](https://learn.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/f/from-vs-on). diff --git a/doc/development/ee_features.md b/doc/development/ee_features.md index 2ce01827e1f5dd..53d3a8d8d1f38d 100644 --- a/doc/development/ee_features.md +++ b/doc/development/ee_features.md @@ -191,14 +191,14 @@ version of the product: only if the project namespace's plan includes the feature. 1. On the left sidebar, at the bottom, select **Admin**. - 1. On the left sidebar, select **Settings** > **General**. + 1. On the left sidebar, select **Settings**** > ****General**. 1. Expand **Account and limit**. 1. Select the **Allow use of licensed EE features** checkbox. 1. Select **Save changes**. 1. Ensure the group you want to test the EE feature for is actually using an EE plan: 1. On the left sidebar, at the bottom, select **Admin**. - 1. On the left sidebar, select **Overview** > **Groups**. + 1. On the left sidebar, select **Overview**** > ****Groups**. 1. Identify the group you want to modify, and select **Edit**. 1. Scroll to **Permissions and group features**. For **Plan**, select `Ultimate`. 1. Select **Save changes**. diff --git a/doc/development/integrations/jenkins.md b/doc/development/integrations/jenkins.md index 9234032cfab18e..8233fa912a4267 100644 --- a/doc/development/integrations/jenkins.md +++ b/doc/development/integrations/jenkins.md @@ -24,7 +24,7 @@ GitLab does not allow requests to localhost or the local network by default. Whe 1. Sign in to your GitLab instance as an administrator. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Network**. +1. Select **Settings** > **Network**. 1. Expand **Outbound requests**, and select the following checkboxes: - **Allow requests to the local network from webhooks and integrations** diff --git a/doc/development/integrations/jira_connect.md b/doc/development/integrations/jira_connect.md index 1111271b0e9216..935f689cb22c91 100644 --- a/doc/development/integrations/jira_connect.md +++ b/doc/development/integrations/jira_connect.md @@ -84,7 +84,7 @@ otherwise the app installation in Jira fails. The following steps describe setting up an environment to test the GitLab OAuth flow: 1. Start a [Gitpod session](#setting-up-gitpod). -1. On your GitLab instance, go to **Admin > Applications**. +1. On your GitLab instance, go to **Admin** > **Applications**. 1. Create a new application with the following settings: - Name: `GitLab for Jira` - Redirect URI: `YOUR_GITPOD_INSTANCE/-/jira_connect/oauth_callbacks` diff --git a/doc/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md b/doc/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md index 353f04087dfaae..c9103225dffb64 100644 --- a/doc/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md +++ b/doc/development/internal_analytics/internal_event_instrumentation/local_setup_and_debugging.md @@ -160,7 +160,7 @@ On GitLab.com events are sent to a collector configured by GitLab. By default, G You can configure your instance to use a custom Snowplow collector. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Snowplow**. 1. Select **Enable Snowplow tracking** and enter your Snowplow configuration information. For example if your custom snowplow collector is available at `your-snowplow-collector.net`: diff --git a/doc/development/internal_analytics/product_analytics.md b/doc/development/internal_analytics/product_analytics.md index e7681cf2dace20..dfead46cd2fd9d 100644 --- a/doc/development/internal_analytics/product_analytics.md +++ b/doc/development/internal_analytics/product_analytics.md @@ -163,7 +163,7 @@ and cascade to all projects by default. To enable product analytics on your instance: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Analytics**. +1. Select **Settings** > **Analytics**. 1. Enter the configuration values. 1. Select **Save changes**. @@ -178,7 +178,7 @@ Prerequisites: - The project must be in a group namespace. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Analytics**. +1. Select **Settings** > **Analytics**. 1. Expand **Data sources** and enter the configuration values. 1. Select **Save changes**. @@ -199,7 +199,7 @@ Onboarding a GitLab project means preparing it to receive events that are used f To onboard a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Analyze > Analytics dashboards**. +1. Select **Analyze** > **Analytics dashboards**. 1. Under **Product analytics**, select **Set up**. Then continue with the setup depending on the provider type. @@ -218,7 +218,7 @@ Prerequisites: 1. Select **Go to analytics settings**. 1. Expand **Data sources** and remove the configuration values. 1. Select **Save changes**. - 1. Select **Analyze > Analytics dashboards**. + 1. Select **Analyze** > **Analytics dashboards**. 1. Under **Product analytics**, select **Set up**. 1. Select **Connect GitLab-managed provider**. @@ -233,7 +233,7 @@ Your instance is being created, and the project onboarded. 1. Select **Go to analytics settings**. 1. Expand **Data sources** and enter the configuration values. 1. Select **Save changes**. - 1. Select **Analyze > Analytics dashboards**. + 1. Select **Analyze** > **Analytics dashboards**. 1. Under **Product analytics**, select **Set up**. 1. Select **Connect your own provider**. @@ -356,7 +356,7 @@ Product analytics usage quota is calculated from the number of events received f To view product analytics usage quota: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > Usage quota**. +1. Select **Settings** > **Usage quota**. 1. Select the **Product analytics** tab. The tab displays the monthly totals for the group and a breakdown of usage per project. diff --git a/doc/development/logs.md b/doc/development/logs.md index f0728360aa6823..ef6919caa6d62b 100644 --- a/doc/development/logs.md +++ b/doc/development/logs.md @@ -57,7 +57,7 @@ Prerequisites: 1. Create an access token: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Settings** > **Access tokens**. + 1. Select **Settings**** > ****Access tokens**. 1. Create an access token with the `api` scope and **Developer** role or greater. Save the access token value for later. 1. To configure your application to send GitLab logs, set the following environment variables: @@ -82,7 +82,7 @@ When you run your application, the OpenTelemetry exporter sends logs to GitLab. You can view the logs for a given project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor** > **Logs**. +1. Select **Monitor**** > ****Logs**. A list of logs is displayed. Currently log date, level, service, and message are supported. Select a log line to view its details. @@ -103,7 +103,7 @@ It is also possible to see log line details such as metadata and resource attrib You can create an issue to track any action taken to resolve or investigate a log. To create an issue for a log: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor** > **Logs**. +1. Select **Monitor**** > ****Logs**. 1. From the list of logs, select a log. 1. In the details drawer, select **Create issue**. @@ -113,7 +113,7 @@ You can edit the issue title and description. ### View issues related to a log 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor** > **Logs**. +1. Select **Monitor**** > ****Logs**. 1. From the list of logs, select a log. 1. In the details drawer, scroll to **Related issues**. 1. Optional. To view the issue details, select an issue. diff --git a/doc/development/metrics.md b/doc/development/metrics.md index b197a75b64c0b9..d37493d4f962e5 100644 --- a/doc/development/metrics.md +++ b/doc/development/metrics.md @@ -56,7 +56,7 @@ You must have at least the Maintainer role for the project. 1. Create an access token: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Settings > Access tokens**. + 1. Select **Settings** > **Access tokens**. 1. Create an access token with the `api` scope and **Developer** role or greater. Save the access token value for later. 1. To configure your application to send GitLab metrics, set the following environment variables: @@ -81,7 +81,7 @@ When you run your application, the OpenTelemetry exporter sends metrics to GitLa You can view the metrics for a given project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor > Metrics**. +1. Select **Monitor** > **Metrics**. A list of metrics is displayed. Select a metric to view its details. @@ -132,7 +132,7 @@ GitLab has a retention limit of 30 days for all ingested metrics. You can create an issue to track any action taken to resolve or investigate a metric. To create an issue for a metric: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor > Metrics**. +1. Select **Monitor** > **Metrics**. 1. From the list of metrics, select a metric. 1. Select **Create issue**. @@ -142,7 +142,7 @@ You can edit the issue title and description. ### View issues related to a metric 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor > Metrics**. +1. Select **Monitor** > **Metrics**. 1. From the list of metrics, select a metric. 1. Scroll to **Related issues**. 1. Optional. To view the issue details, select an issue. diff --git a/doc/development/tracing.md b/doc/development/tracing.md index a6783b0700d5db..be3de2f1435d01 100644 --- a/doc/development/tracing.md +++ b/doc/development/tracing.md @@ -61,7 +61,7 @@ Prerequisites: 1. Create an access token: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Settings > Access tokens**. + 1. Select **Settings** > **Access tokens**. 1. Create an access token with the `api` scope and **Developer** role or greater. Save the access token value for later. 1. To configure your application to send GitLab traces, set the following environment variables: @@ -88,7 +88,7 @@ If your traces are exported successfully, you can see them in the project. To view the list of traces: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor > Traces**. +1. Select **Monitor** > **Traces**. 1. Optional. To view the details of a trace, select it from the list. ![list of traces](img/tracing_list_v16_11.png) @@ -106,7 +106,7 @@ To view the list of traces: You can create an issue to track any action taken to resolve or investigate a trace. To create an issue for a trace: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor > Traces**. +1. Select **Monitor** > **Traces**. 1. From the list of traces, select a trace. 1. Select **Create issue**. @@ -116,7 +116,7 @@ You can edit the issue title and description. ## View issues related to a trace 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Monitor > Traces**. +1. Select **Monitor** > **Traces**. 1. From the list of traces, select a trace. 1. Scroll to **Related issues**. 1. Optional. To view the issue details, select an issue. diff --git a/doc/install/aws/_index.md b/doc/install/aws/_index.md index bda805079bc525..4c61d5d55b3aa1 100644 --- a/doc/install/aws/_index.md +++ b/doc/install/aws/_index.md @@ -239,7 +239,7 @@ it receive traffic from any destination. 1. Select **Route Tables** from the left menu and select the `gitlab-public` route to show the options at the bottom. -1. Select the **Routes** tab, select **Edit routes** > **Add route** and set `0.0.0.0/0` +1. Select the **Routes** tab, select **Edit routes**** > ****Add route** and set `0.0.0.0/0` as the destination. In the target column, select the **Internet Gateway** and select the `gitlab-gateway` we created previously. Select **Save changes** when done. @@ -568,7 +568,7 @@ Because we're adding our SSL certificate at the load balancer, we do not need th From your GitLab instance, connect to the RDS instance to verify access and to install the required `pg_trgm` and `btree_gist` extensions. -To find the host or endpoint, go to **Amazon RDS** > **Databases** and select the database you created earlier. Look for the endpoint under the **Connectivity & security** tab. +To find the host or endpoint, go to **Amazon RDS**** > ****Databases** and select the database you created earlier. Look for the endpoint under the **Connectivity & security** tab. Do not to include the colon and port number: diff --git a/doc/install/azure/_index.md b/doc/install/azure/_index.md index 9c04326926cfac..108d8832187a32 100644 --- a/doc/install/azure/_index.md +++ b/doc/install/azure/_index.md @@ -176,7 +176,7 @@ redirect you to the public IP. To set up the GitLab external URL: -1. Connect to GitLab through SSH by going to **Settings** > **Connect** from the VM +1. Connect to GitLab through SSH by going to **Settings**** > ****Connect** from the VM dashboard, and follow the instructions. Remember to sign in with the username and SSH key you specified when you [created the VM](#configure-the-basics-tab). The Azure VM domain name is the one you @@ -258,7 +258,7 @@ in this section whenever you need to update GitLab. To determine the version of GitLab you're currently running: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Overview** > **Dashboard**. +1. Select **Overview**** > ****Dashboard**. 1. Find the version under the **Components** table. If there's a newer available version of GitLab that contains one or more diff --git a/doc/install/install_ai_gateway.md b/doc/install/install_ai_gateway.md index d3f8049f80732e..04c89b2c90e4bc 100644 --- a/doc/install/install_ai_gateway.md +++ b/doc/install/install_ai_gateway.md @@ -371,7 +371,7 @@ If access issues persist, check that authentication is correctly configured, and In case of persistent issues, the error message may suggest bypassing authentication with `AIGW_AUTH__BYPASS_EXTERNAL=true`, but only do this for troubleshooting. -You can also run a [health check](../user/gitlab_duo/setup.md#run-a-health-check-for-gitlab-duo) by going to **Admin** > **GitLab Duo**. +You can also run a [health check](../user/gitlab_duo/setup.md#run-a-health-check-for-gitlab-duo) by going to **Admin**** > ****GitLab Duo**. These tests are performed for offline environments: diff --git a/doc/integration/advanced_search/elasticsearch.md b/doc/integration/advanced_search/elasticsearch.md index 8abbd167311e59..f628174bc59286 100644 --- a/doc/integration/advanced_search/elasticsearch.md +++ b/doc/integration/advanced_search/elasticsearch.md @@ -269,7 +269,7 @@ To set an IAM ARN as a master user, you must use AWS OpenSearch Service with IAM credentials on your GitLab instance: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Advanced Search**. 1. In the **AWS OpenSearch IAM credentials** section: 1. Select the **Use AWS OpenSearch Service with IAM credentials** checkbox. @@ -300,7 +300,7 @@ To create a master user, you must configure the OpenSearch domain URL and the master username and password on your GitLab instance: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Advanced Search**. 1. In **OpenSearch domain URL**, enter the URL to the OpenSearch domain endpoint. 1. In **Username**, enter the master username. @@ -423,7 +423,7 @@ Prerequisites: To enable advanced search: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Configure the [advanced search settings](#advanced-search-configuration) for your Elasticsearch cluster. Do not select the **Search with Elasticsearch enabled** checkbox yet. 1. [Index the instance](#index-the-instance). @@ -460,7 +460,7 @@ You can perform initial indexing or re-create an index from the user interface. To enable advanced search and index the instance from the user interface: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Select the **Elasticsearch indexing** checkbox, then select **Save changes**. 1. Select **Index the instance**. @@ -513,7 +513,7 @@ Prerequisites: To check indexing status: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Indexing status**. ### Monitor the status of background jobs @@ -525,7 +525,7 @@ Prerequisites: To monitor the status of background jobs: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Monitoring > Background jobs**. +1. Select **Monitoring** > **Background jobs**. 1. On the Sidekiq dashboard, select **Queues** and wait for the `elastic_commit_indexer` and `elastic_wiki_indexer` queues to drop to `0`. These queues contain jobs to index code and wiki data for projects and groups. @@ -627,7 +627,7 @@ For example, if you index two separate groups, you must run separate code search To enable global search for limited indexing: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Advanced search** 1. Select **Enable global search for limited indexing**. 1. Select **Save changes**. @@ -647,7 +647,7 @@ To enable custom language analyzers: 1. Install the desired plugins, refer to [Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/plugins/7.9/installation.html) for plugins installation instructions. The plugins must be installed on every node in the cluster, and each node must be restarted after installation. For a list of plugins, see the table later in this section. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Locate **Custom analyzers: language support**. 1. Enable plugins support for **Indexing**. 1. Select **Save changes** for the changes to take effect. @@ -672,7 +672,7 @@ Prerequisites: To disable advanced search in GitLab: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Clear the **Elasticsearch indexing** and **Search with Elasticsearch enabled** checkboxes. 1. Select **Save changes**. 1. Optional. For Elasticsearch instances that are still online, delete existing indices: @@ -694,7 +694,7 @@ Prerequisites: To resume indexing: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Advanced Search**. 1. Clear the **Pause Elasticsearch indexing** checkbox. @@ -721,7 +721,7 @@ To trigger reindexing: 1. Sign in to your GitLab instance as an administrator. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Elasticsearch zero-downtime reindexing**. 1. Select **Trigger cluster reindexing**. @@ -742,7 +742,7 @@ Prerequisites: To trigger zero-downtime reindexing: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Elasticsearch zero-downtime reindexing**. The following settings are available: @@ -794,7 +794,7 @@ To abandon an unfinished reindexing job and resume indexing: ``` 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Advanced Search**. 1. Clear the **Pause Elasticsearch indexing** checkbox. @@ -899,7 +899,7 @@ debug why the migration was halted and make any changes before retrying the migr When you believe you've fixed the cause of the failure: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Advanced Search**. 1. Inside the **Elasticsearch migration halted** alert box, select **Retry migration**. The migration is scheduled to be retried in the background. diff --git a/doc/integration/akismet.md b/doc/integration/akismet.md index 511dd679e88fb7..20b9aa638c838e 100644 --- a/doc/integration/akismet.md +++ b/doc/integration/akismet.md @@ -47,7 +47,7 @@ To use Akismet: 1. Select **Show** to reveal the API key, and copy the API key's value. 1. Sign in to GitLab as an administrator. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Reporting**. +1. Select **Settings** > **Reporting**. 1. Expand **Spam and Anti-bot Protection**. 1. Select the **Enable Akismet** checkbox. 1. Fill in the API key from step 3. diff --git a/doc/integration/datadog.md b/doc/integration/datadog.md index 7d67bbc26d1dda..d23876507b1601 100644 --- a/doc/integration/datadog.md +++ b/doc/integration/datadog.md @@ -29,7 +29,7 @@ or for a specific project or group: 1. *For integrations for the entire instance:* 1. Sign in to GitLab as a user with administrator access. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Integrations**. +1. Select **Settings** > **Integrations**. 1. Scroll to **Add an integration**, and select **Datadog**. 1. Select **Active** to enable the integration. 1. Specify the [**Datadog site**](https://docs.datadoghq.com/getting_started/site/) to send data to. diff --git a/doc/integration/diffblue_cover.md b/doc/integration/diffblue_cover.md index 4fad1a7bd5ec7a..ed5c7a22b14354 100644 --- a/doc/integration/diffblue_cover.md +++ b/doc/integration/diffblue_cover.md @@ -36,7 +36,7 @@ To integrate Diffblue Cover into your pipeline: 1. On the left sidebar, select **Search or go to** and find your project. - If you want to test the integration with a sample project, you can [import](../user/project/import/repo_by_url.md) the Diffblue [Spring PetClinic sample project](https://github.com/diffblue/demo-spring-petclinic). -1. Select **Settings > Integrations**. +1. Select **Settings** > **Integrations**. 1. Find **Diffblue Cover** and select **Configure**. 1. Complete the fields: diff --git a/doc/integration/elasticsearch/troubleshooting/access.md b/doc/integration/elasticsearch/troubleshooting/access.md index d514a2afc678dd..3b991ba6c6194a 100644 --- a/doc/integration/elasticsearch/troubleshooting/access.md +++ b/doc/integration/elasticsearch/troubleshooting/access.md @@ -94,7 +94,7 @@ To verify that your GitLab instance is using Elasticsearch: - When you perform a search, in the upper-right corner of the search results page, ensure **Advanced search is enabled** is displayed. -- In the **Admin** area, under **Settings > Search**, check that the +- In the **Admin** area, under **Settings** > **Search**, check that the advanced search settings are selected. Those same settings there can be obtained from the Rails console if necessary: diff --git a/doc/integration/elasticsearch/troubleshooting/indexing.md b/doc/integration/elasticsearch/troubleshooting/indexing.md index e7827462f57d48..5ab5f54019bc59 100644 --- a/doc/integration/elasticsearch/troubleshooting/indexing.md +++ b/doc/integration/elasticsearch/troubleshooting/indexing.md @@ -281,7 +281,7 @@ These settings limit indexing to 2000 documents per minute. To adjust worker settings: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Advanced Search**. 1. Select the **Requeue indexing workers** checkbox. 1. In the **Number of shards for non-code indexing** text box, enter a value higher than `2`. diff --git a/doc/integration/exact_code_search/zoekt.md b/doc/integration/exact_code_search/zoekt.md index 134e79b5071ac8..62c02a6f2afc35 100644 --- a/doc/integration/exact_code_search/zoekt.md +++ b/doc/integration/exact_code_search/zoekt.md @@ -65,7 +65,7 @@ Prerequisites: To enable [exact code search](../../user/search/exact_code_search.md) in GitLab: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. Select the **Enable indexing** and **Enable searching** checkboxes. 1. Select **Save changes**. @@ -128,7 +128,7 @@ Prerequisites: To pause indexing for [exact code search](../../user/search/exact_code_search.md): 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. Select the **Pause indexing** checkbox. 1. Select **Save changes**. @@ -152,7 +152,7 @@ You can index both existing and new root namespaces automatically. To index all root namespaces automatically: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. Select the **Index root namespaces automatically** checkbox. 1. Select **Save changes**. @@ -187,7 +187,7 @@ This feature is enabled by default and caches results for five minutes. To cache search results: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. Select the **Cache search results for five minutes** checkbox. 1. Select **Save changes**. @@ -214,7 +214,7 @@ You can adjust this value based on the node's performance and workload. To set the number of concurrent indexing tasks: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. In the **Indexing CPU to tasks multiplier** text box, enter a value. @@ -244,7 +244,7 @@ You can adjust this value based on the node's performance and workload. To set the number of parallel processes per indexing task: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. In the **Number of parallel processes per indexing task** text box, enter a value. 1. Select **Save changes**. @@ -268,7 +268,7 @@ You can adjust this value based on the node's performance and workload. To set the number of namespaces per indexing rollout: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. In the **Number of namespaces per indexing rollout** text box, enter a number greater than zero. @@ -295,7 +295,7 @@ Use this setting to manage your Zoekt infrastructure and prevent orphaned resour To define when offline nodes are automatically deleted: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. In the **Offline nodes automatically deleted after** text box, enter a value (for example, `30m` (30 minutes), `2h` (two hours), or `1d` (one day)). @@ -320,7 +320,7 @@ The default value is `30m` (30 minutes). To define the indexing timeout for a project: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. In the **Indexing timeout per project** text box, enter a value (for example, `30m` (30 minutes), `2h` (two hours), or `1d` (one day)). @@ -347,7 +347,7 @@ You can adjust this value based on the node's performance and workload. To set the maximum number of files in a project to be indexed: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. In the **Maximum number of files per project to be indexed** text box, enter a number greater than zero. 1. Select **Save changes**. @@ -371,7 +371,7 @@ A value of `0` means failed namespaces never retry. To define the retry interval for failed namespaces: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Exact code search configuration**. 1. In the **Retry interval for failed namespaces** text box, enter a value (for example, `30m` (30 minutes), `2h` (two hours), or `1d` (one day)). diff --git a/doc/integration/external-issue-tracker.md b/doc/integration/external-issue-tracker.md index fa1c2381fe1c99..2ba753eee53a8b 100644 --- a/doc/integration/external-issue-tracker.md +++ b/doc/integration/external-issue-tracker.md @@ -32,7 +32,7 @@ References are displayed as issue links. To disable the GitLab issue tracker for a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. Under **Issues**, turn off the toggle. 1. Select **Save changes**. diff --git a/doc/integration/gitpod.md b/doc/integration/gitpod.md index 033bbab0f9c222..f2eda81ef9a064 100644 --- a/doc/integration/gitpod.md +++ b/doc/integration/gitpod.md @@ -54,7 +54,7 @@ For GitLab Self-Managed, a GitLab administrator must: 1. Enable the Gitpod integration in GitLab: 1. On the left sidebar, at the bottom, select **Admin**. - 1. On the left sidebar, select **Settings > General**. + 1. On the left sidebar, select **Settings** > **General**. 1. Expand the **Gitpod** configuration section. 1. Select the **Enable Gitpod integration** checkbox. 1. Enter the Gitpod instance URL (for example, `https://gitpod.example.com` or `https://gitpod.io`). @@ -70,10 +70,10 @@ you can launch it from GitLab in one of these ways: - From a project repository: 1. On the left sidebar, select **Search or go to** and find your project. - 1. In the upper right, select **Code > Gitpod**. + 1. In the upper right, select **Code** > **Gitpod**. - From a merge request: 1. Go to your merge request. - 1. In the upper-right corner, select **Code > Open in Gitpod**. + 1. In the upper-right corner, select **Code** > **Open in Gitpod**. Gitpod builds your development environment for your branch. diff --git a/doc/integration/google_cloud_iam.md b/doc/integration/google_cloud_iam.md index 154dd3e15c7fb8..1056e29245e155 100644 --- a/doc/integration/google_cloud_iam.md +++ b/doc/integration/google_cloud_iam.md @@ -96,7 +96,7 @@ To set up the Workload Identity Federation you can either: To use the GitLab UI to set up the Workload Identity Federation: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Integrations**. +1. Select **Settings** > **Integrations**. 1. Locate the Google Cloud IAM integration and select **Configure**. 1. Select **Guided setup** and follow the instructions. @@ -190,7 +190,7 @@ For more information, see the Google Cloud documentation about how to [define an After you create the workload identity pool and provider, to complete the setup in GitLab: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Integrations**. +1. Select **Settings** > **Integrations**. 1. Locate the Google Cloud IAM integration and select **Configure**. 1. Select **Manual setup** 1. Complete the fields. diff --git a/doc/integration/jenkins.md b/doc/integration/jenkins.md index 1620280c806804..f77eb9f196820d 100644 --- a/doc/integration/jenkins.md +++ b/doc/integration/jenkins.md @@ -65,11 +65,11 @@ To configure a Jenkins integration with GitLab: Install and configure the Jenkins plugin to authorize the connection to GitLab. -1. On the Jenkins server, select **Manage Jenkins > Manage Plugins**. +1. On the Jenkins server, select **Manage Jenkins** > **Manage Plugins**. 1. Select the **Available** tab. Search for `gitlab-plugin` and select it to install. See the [Jenkins GitLab documentation](https://plugins.jenkins.io/gitlab-plugin/) for other ways to install the plugin. -1. Select **Manage Jenkins > Configure System**. +1. Select **Manage Jenkins** > **Configure System**. 1. In the **GitLab** section, select **Enable authentication for '/project' end-point**. 1. Select **Add**, then choose **Jenkins Credential Provider**. 1. Select **GitLab API token** as the token type. @@ -132,7 +132,7 @@ You should use this approach for Jenkins integrations if you can provide GitLab with your Jenkins server URL and authentication information. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Integrations**. +1. Select **Settings** > **Integrations**. 1. Select **Jenkins**. 1. Select the **Active** checkbox. 1. Select the events you want GitLab to trigger a Jenkins build for: diff --git a/doc/integration/jira/configure.md b/doc/integration/jira/configure.md index 7fcf0d55e26a81..32843977301676 100644 --- a/doc/integration/jira/configure.md +++ b/doc/integration/jira/configure.md @@ -57,7 +57,7 @@ With this integration, your GitLab project can interact with all Jira projects o To configure your project settings in GitLab: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Integrations**. +1. Select **Settings** > **Integrations**. 1. Select **Jira issues**. 1. Under **Enable integration**, select the **Active** checkbox. 1. Provide connection details: @@ -142,7 +142,7 @@ You can enable Jira issues for a specific group or project, but you can view the To view issues from one or more Jira projects in a GitLab project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Jira issues**. +1. Select **Plan** > **Jira issues**. By default, the issues are sorted by **Created date**. The most recently created issues appear at the top. @@ -209,7 +209,7 @@ You can create a Jira issue from GitLab to track any action taken to resolve or To create a Jira issue for a vulnerability: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Select the vulnerability's description. 1. Select **Create Jira issue**. diff --git a/doc/integration/jira/connect-app.md b/doc/integration/jira/connect-app.md index 51dbe201955041..497d24f7bc5104 100644 --- a/doc/integration/jira/connect-app.md +++ b/doc/integration/jira/connect-app.md @@ -63,7 +63,7 @@ Prerequisites: To install the GitLab for Jira Cloud app: -1. In Jira, on the top bar, select **Apps > Explore more apps** and search for `GitLab for Jira Cloud`. +1. In Jira, on the top bar, select **Apps** > **Explore more apps** and search for `GitLab for Jira Cloud`. 1. Select **GitLab for Jira Cloud**, then select **Get it now**. Alternatively, [get the app directly from the Atlassian Marketplace](https://marketplace.atlassian.com/apps/1221011/gitlab-com-for-jira-cloud?tab=overview&hosting=cloud). @@ -100,7 +100,7 @@ To configure the GitLab for Jira Cloud app: -1. In Jira, on the top bar, select **Apps > Manage your apps**. +1. In Jira, on the top bar, select **Apps** > **Manage your apps**. 1. Expand **GitLab for Jira**. Depending on how you installed the app, the name of the app is: - **GitLab for Jira (gitlab.com)** if you [installed the app from the Atlassian Marketplace](https://marketplace.atlassian.com/apps/1221011/gitlab-com-for-jira-cloud?tab=overview&hosting=cloud). - **GitLab for Jira (``)** if you [installed the app manually](../../administration/settings/jira_cloud_app.md#install-the-gitlab-for-jira-cloud-app-manually). @@ -160,13 +160,13 @@ and not through the GitLab integrations form or API. In Jira Service Management: -1. In your service project, go to **Project settings > Change management**. -1. Select **Connect Pipeline > GitLab**, then copy the **Service ID** at the end of the setup flow. +1. In your service project, go to **Project settings** > **Change management**. +1. Select **Connect Pipeline** > **GitLab**, then copy the **Service ID** at the end of the setup flow. In GitLab: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Integrations**. +1. Select **Settings** > **Integrations**. 1. Select **GitLab for Jira Cloud app**. If the integration is disabled, first [link a GitLab group](#configure-the-gitlab-for-jira-cloud-app) which enables the GitLab for Jira Cloud app integration for the group, its subgroups, and projects. 1. In the **Service ID** field, enter the service ID that you want to map into this project. To use multiple service IDs, @@ -223,7 +223,7 @@ To enable deployment gating: - In GitLab: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Settings > Integrations**. + 1. Select **Settings** > **Integrations**. 1. Select **GitLab for Jira Cloud app**. 1. Under **Deployment gating**, select the **Enable deployment gating** checkbox. 1. In the **Environment tiers** text box, enter the names of the environments you want to enable deployment gating for. @@ -356,8 +356,8 @@ In Bitbucket: In Jira: 1. In **Projects**, select your project. -1. Select **Development > Code**. -1. Select **Connect Bitbucket > Link Bitbucket Cloud workspace**. +1. Select **Development** > **Code**. +1. Select **Connect Bitbucket** > **Link Bitbucket Cloud workspace**. 1. Select the workspace you created in Bitbucket. 1. Select **Grant access**. diff --git a/doc/integration/jira/dvcs/troubleshooting.md b/doc/integration/jira/dvcs/troubleshooting.md index 7b32d479647037..c6cb5b6be9fbf6 100644 --- a/doc/integration/jira/dvcs/troubleshooting.md +++ b/doc/integration/jira/dvcs/troubleshooting.md @@ -128,7 +128,7 @@ In the previous example, the merge requests feature is disabled. To resolve the issue, enable the relevant feature: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. Use the toggles to enable the features as needed. @@ -137,7 +137,7 @@ To resolve the issue, enable the relevant feature: To find webhook logs in a DVCS-linked project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Webhooks**. +1. Select **Settings** > **Webhooks**. 1. Scroll down to **Project hooks**. 1. Next to the log that points to your Jira instance, select **Edit**. 1. Scroll down to **Recent events**. diff --git a/doc/integration/jira/issues.md b/doc/integration/jira/issues.md index c1f8f6342a2e13..6fee188c8d4168 100644 --- a/doc/integration/jira/issues.md +++ b/doc/integration/jira/issues.md @@ -66,7 +66,7 @@ With this integration, you can prevent merge requests from being merged if they To enable this feature: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Merge requests**. +1. Select **Settings** > **Merge requests**. 1. In the **Merge checks** section, select **Require an associated issue from Jira**. 1. Select **Save**. @@ -104,7 +104,7 @@ The regex pattern must follow the [RE2 syntax](https://github.com/google/re2/wik To define a regex pattern for Jira issue keys: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Integrations**. +1. Select **Settings** > **Integrations**. 1. Select **Jira issues**. 1. Go to the **Jira issue matching** section. 1. In the **Jira issue regex** text box, enter a regex pattern. @@ -128,7 +128,7 @@ GitLab matches `JIRA#ALPHA-1` rather than `ALPHA-1`. To define a prefix for Jira issue keys: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Integrations**. +1. Select **Settings** > **Integrations**. 1. Select **Jira issues**. 1. Go to the **Jira issue matching** section. 1. In the **Jira issue prefix** text box, enter a prefix. diff --git a/doc/integration/kerberos.md b/doc/integration/kerberos.md index f917f6ccf2aee3..9687db16c378fd 100644 --- a/doc/integration/kerberos.md +++ b/doc/integration/kerberos.md @@ -125,7 +125,7 @@ If you're an administrator, you can link a Kerberos account to an existing GitLab account. To do so: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Overview > Users**. +1. Select **Overview** > **Users**. 1. Select a user, then select the **Identities** tab. 1. From the **Provider** dropdown list, select **Kerberos**. 1. Make sure the **Identifier** corresponds to the Kerberos username. @@ -166,7 +166,7 @@ With that information at hand: 1. As an administrator, you can confirm the new, blocked account: 1. On the left sidebar, at the bottom, select **Admin**. - 1. On the left sidebar, select **Overview > Users** and review the **Blocked** tab. + 1. On the left sidebar, select **Overview** > **Users** and review the **Blocked** tab. 1. You can enable the user. 1. If `block_auto_created_users` is false, the Kerberos user is authenticated and is signed in to GitLab. diff --git a/doc/integration/mattermost/_index.md b/doc/integration/mattermost/_index.md index 6c3becd03e105c..59838191bfeca4 100644 --- a/doc/integration/mattermost/_index.md +++ b/doc/integration/mattermost/_index.md @@ -141,12 +141,12 @@ By default GitLab Mattermost requires all users to sign up with GitLab and disab ### Reauthorize GitLab Mattermost To reauthorize GitLab Mattermost, you first need to revoke the existing -authorization. This can be done in the **Settings > Applications** area of GitLab. Then follow the steps +authorization. This can be done in the **Settings** > **Applications** area of GitLab. Then follow the steps in the following section to complete authorization. ### Authorize GitLab Mattermost -Go to the **Settings > Applications** area in GitLab. Create a new application and for the **Redirect URI** use the following (replace `http` with `https` if you use HTTPS): +Go to the **Settings** > **Applications** area in GitLab. Create a new application and for the **Redirect URI** use the following (replace `http` with `https` if you use HTTPS): ```plaintext http://mattermost.example.com/signup/gitlab/complete @@ -326,7 +326,7 @@ The plugin and slash commands can be used together or individually. ### Setting up SMTP for GitLab Mattermost These settings are configured through the Mattermost System Console by the System Administrator. -On the **Environment > SMTP** tab of the **System Console**, you can enter the SMTP credentials given by your SMTP provider, or `127.0.0.1` and port `25` to use `sendmail`. More information on the specific settings +On the **Environment** > **SMTP** tab of the **System Console**, you can enter the SMTP credentials given by your SMTP provider, or `127.0.0.1` and port `25` to use `sendmail`. More information on the specific settings that are needed is available in the [Mattermost documentation](https://docs.mattermost.com/install/smtp-email-setup.html). These settings can also be configured in `/var/opt/gitlab/mattermost/config.json`. @@ -335,7 +335,7 @@ These settings can also be configured in `/var/opt/gitlab/mattermost/config.json Enabling this feature allows users to control how often they receive email notifications. -Email batching can be enabled in the Mattermost **System Console** by navigating to the **Environment > SMTP** tab, and setting the **Enable Email Batching** setting to **True**. +Email batching can be enabled in the Mattermost **System Console** by navigating to the **Environment** > **SMTP** tab, and setting the **Enable Email Batching** setting to **True**. This setting can also be configured in `/var/opt/gitlab/mattermost/config.json`. diff --git a/doc/integration/oauth_provider.md b/doc/integration/oauth_provider.md index 68000a81179414..5da7f88cff0904 100644 --- a/doc/integration/oauth_provider.md +++ b/doc/integration/oauth_provider.md @@ -59,7 +59,7 @@ To create a new application for your user: To create a new application for a group: 1. Go to the desired group. -1. On the left sidebar, select **Settings > Applications**. +1. On the left sidebar, select **Settings** > **Applications**. 1. Enter a **Name** and **Redirect URI**. 1. Select OAuth 2 scopes as defined in [Authorized Applications](#view-all-authorized-applications). 1. In the **Redirect URI**, enter the URL where users are sent after they authorize with GitLab. diff --git a/doc/integration/omniauth.md b/doc/integration/omniauth.md index caa8f16f7f5679..1fa5b0272c4c4a 100644 --- a/doc/integration/omniauth.md +++ b/doc/integration/omniauth.md @@ -288,7 +288,7 @@ By default, sign-in is enabled for all the OAuth providers configured in `config To enable or disable an OmniAuth provider: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Sign-in restrictions**. 1. In the **Enabled OAuth authentication sources** section, select or clear the checkbox for each provider you want to enable or disable. diff --git a/doc/integration/recaptcha.md b/doc/integration/recaptcha.md index 797c813a62c956..97a46a3c5d7d11 100644 --- a/doc/integration/recaptcha.md +++ b/doc/integration/recaptcha.md @@ -24,7 +24,7 @@ To use reCAPTCHA, first create a site and private key. 1. To get reCAPTCHA v2 keys, fill in the form and select **Submit**. 1. Sign in to your GitLab server as an administrator. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Reporting**. +1. Select **Settings** > **Reporting**. 1. Expand **Spam and Anti-bot Protection**. 1. In the reCAPTCHA fields, enter the keys you obtained in the previous steps. 1. Select the **Enable reCAPTCHA** checkbox. diff --git a/doc/integration/snowflake.md b/doc/integration/snowflake.md index f32e6afeea2621..d8f00406f19196 100644 --- a/doc/integration/snowflake.md +++ b/doc/integration/snowflake.md @@ -35,9 +35,9 @@ requires both Snowflake and GitLab configuration. ## Configure the GitLab Data Connector 1. Sign in to Snowflake. -1. Select **Data Products > Marketplace**. +1. Select **Data Products** > **Marketplace**. 1. Search for **GitLab Data Connector**. -1. Select **Data Products > Apps**. +1. Select **Data Products** > **Apps**. 1. Select **GitLab Data Connector**. 1. Select a [warehouse](https://docs.snowflake.com/en/user-guide/warehouses) where the GitLab Data Connector runs. 1. Select **Start Configuration**. @@ -55,5 +55,5 @@ requires both Snowflake and GitLab configuration. ## View data in Snowflake 1. Sign in to Snowflake. -1. Select **Data > Databases**. +1. Select **Data** > **Databases**. 1. Select the warehouse previously configured. diff --git a/doc/integration/sourcegraph.md b/doc/integration/sourcegraph.md index 3f4711365ea040..679f266255bc59 100644 --- a/doc/integration/sourcegraph.md +++ b/doc/integration/sourcegraph.md @@ -73,7 +73,7 @@ Prerequisites: - You must be an administrator. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Sourcegraph**. 1. Select **Enable Sourcegraph**. 1. Optional. Select **Block on private and internal projects**. diff --git a/doc/security/compliance_security_policy_management.md b/doc/security/compliance_security_policy_management.md index 46f87453ae4369..cc106a8e4bf5ae 100644 --- a/doc/security/compliance_security_policy_management.md +++ b/doc/security/compliance_security_policy_management.md @@ -53,7 +53,7 @@ You can designate a CSP group using either the GitLab UI or the REST API. #### Using the GitLab UI -1. Go to **Admin Area**** > ****Settings**** > ****Security and Compliance**. +1. Go to **Admin Area****** > ******Settings****** > ******Security and Compliance**. 1. In the **Designate CSP Group** section, select an existing top-level group from the dropdown list. 1. Select **Save changes**. @@ -113,7 +113,7 @@ Instance administrators can: Group administrators and owners can: -- View all applicable policies in **Secure**** > ****Policies**, including both locally-defined and centrally-managed policies. +- View all applicable policies in **Secure****** > ******Policies**, including both locally-defined and centrally-managed policies. - Create team-specific policies in addition to centrally-managed ones. - Understand policy sources with clear indicators that show whether policies come from your team or central administration. @@ -127,7 +127,7 @@ The **Policies** page displays only the policies from the CSP that are currently Project administrators and owners can: -- View all applicable policies in **Secure**** > ****Policies**, including both locally-defined and centrally-managed policies. +- View all applicable policies in **Secure****** > ******Policies**, including both locally-defined and centrally-managed policies. - Create project-specific policies in addition to centrally-managed ones. - Understand policy sources with clear indicators that show whether policies come from your project, group, or central administration. @@ -141,7 +141,7 @@ The **Policies** page displays only the policies from the CSP that are currently Developers can: -- View all security policies that apply to your work in the **Secure**** > ****Policies**. +- View all security policies that apply to your work in the **Secure****** > ******Policies**. - Understand security and compliance requirements with clear visibility into centrally-mandated policies. ## Beta considerations diff --git a/doc/security/hardening_application_recommendations.md b/doc/security/hardening_application_recommendations.md index 5dc58888e3450d..f4461af7fe87ba 100644 --- a/doc/security/hardening_application_recommendations.md +++ b/doc/security/hardening_application_recommendations.md @@ -57,7 +57,7 @@ the documentation on [deploy keys](../user/project/deploy_keys/_index.md) and ## General 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **General**. +1. Select **Settings**** > ****General**. Hardening adjustments can be made in 4 sections. @@ -175,7 +175,7 @@ For more detailed information, see ## Integrations 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **Integrations**. +1. Select **Settings**** > ****Integrations**. In general, as long as administrators control and monitor usage, integrations are fine in a hardened environment. Be cautious about integrations that allow @@ -186,7 +186,7 @@ process or authenticated user. ## Metrics and profiling 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **Metrics and profiling**. +1. Select **Settings**** > ****Metrics and profiling**. The main focus for hardening is **Usage statistics**: @@ -201,7 +201,7 @@ The main focus for hardening is **Usage statistics**: ## Network 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **Network**. +1. Select **Settings**** > ****Network**. For any setting that enables rate limiting, make sure it is selected. Default values should be fine. Additionally there are numerous settings that enable access, and all diff --git a/doc/security/password_length_limits.md b/doc/security/password_length_limits.md index ecc708021d2a29..bba37aecedc979 100644 --- a/doc/security/password_length_limits.md +++ b/doc/security/password_length_limits.md @@ -28,7 +28,7 @@ The user password length is set to a minimum of 8 characters by default. To change the minimum password length using GitLab UI: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **General**. +1. Select **Settings**** > ****General**. 1. Expand **Sign-up restrictions**. 1. Enter a **Minimum password length** value greater than or equal to `8`. 1. Select **Save changes**. diff --git a/doc/security/reset_user_password.md b/doc/security/reset_user_password.md index e2250e92b11a5d..5d6bb1bd479180 100644 --- a/doc/security/reset_user_password.md +++ b/doc/security/reset_user_password.md @@ -25,7 +25,7 @@ You can reset user passwords by using the UI, a Rake task, a Rails console, or t To reset a user password in the UI: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Overview** > **Users**. +1. Select **Overview**** > ****Users**. 1. Identify a user account to update, select **Edit**. 1. In the **Password** section, enter and confirm a new password. 1. Select **Save changes**. diff --git a/doc/security/ssh_keys_restrictions.md b/doc/security/ssh_keys_restrictions.md index 3c0b180863dadb..218965f3de9290 100644 --- a/doc/security/ssh_keys_restrictions.md +++ b/doc/security/ssh_keys_restrictions.md @@ -27,7 +27,7 @@ GitLab allows you to restrict the allowed SSH key technology as well as specify the minimum key length for each technology: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **General** . +1. Select **Settings**** > ****General** . 1. Expand **Visibility and access controls** and set your desired values for each key type: - **RSA SSH keys**. - **DSA SSH keys**. diff --git a/doc/security/tokens/_index.md b/doc/security/tokens/_index.md index a63bd9316e09e1..c36b983a78040a 100644 --- a/doc/security/tokens/_index.md +++ b/doc/security/tokens/_index.md @@ -297,7 +297,7 @@ Prerequisites: - You must be an administrator. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **General**. +1. Select **Settings**** > ****General**. 1. Expand **Visibility and access controls**. 1. Under **Feed token**, select the **Disable feed token** checkbox, then select **Save changes**. diff --git a/doc/security/two_factor_authentication.md b/doc/security/two_factor_authentication.md index 30c8370d1eb407..a2d71e2505b5cb 100644 --- a/doc/security/two_factor_authentication.md +++ b/doc/security/two_factor_authentication.md @@ -50,7 +50,7 @@ You can use the UI or the API to enforce 2FA for all users. ### Use the UI 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **General**. +1. Select **Settings**** > ****General**. 1. Expand **Sign-in restrictions**: - Select **Enforce two-factor authentication** to enable this feature. - In **Two-factor grace period**, enter a number of hours. If you want to @@ -83,7 +83,7 @@ For more information, see the [list of settings that can be accessed through API Administrators can enforce 2FA for administrator users in a GitLab Self-Managed instance. 1. On the left sidebar, at the bottom, select **Admin**. -1. On the left sidebar, select **Settings** > **General**. +1. On the left sidebar, select **Settings**** > ****General**. 1. Expand the **Sign-in restrictions** section: 1. Select **Require administrators to enable 2FA**. 1. In **Two-factor grace period**, enter a number of hours. If you want to @@ -121,7 +121,7 @@ Prerequisites: To enforce 2FA for a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings** > **General**. +1. Select **Settings**** > ****General**. 1. Expand **Permissions and group features**. 1. Select **All users in this group must set up two-factor authentication**. 1. Optional. In **Delay 2FA enforcement (hours)**, enter the number of hours you @@ -148,7 +148,7 @@ In such cases, the most restrictive requirement takes precedence. To prevent subgroups from setting individual 2FA requirements: -1. Go to the top-level group's **Settings** > **General**. +1. Go to the top-level group's **Settings**** > ****General**. 1. Expand the **Permissions and group features** section. 1. Clear the **Allow subgroups to set up their own two-factor authentication rule** checkbox. @@ -250,7 +250,7 @@ Top-level group Owners can disable two-factor authentication (2FA) for enterpris To disable 2FA: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage** > **Members**. +1. Select **Manage**** > ****Members**. 1. Find a user with the **Enterprise** and **2FA** badges. 1. Select **More actions** ({{< icon name="ellipsis_v" >}}) and select **Disable two-factor authentication**. diff --git a/doc/security/unlock_user.md b/doc/security/unlock_user.md index 913207fdcf4ec7..45e649d559388a 100644 --- a/doc/security/unlock_user.md +++ b/doc/security/unlock_user.md @@ -53,7 +53,7 @@ Prerequisites To unlock an account from the Admin area: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Overview** > **Users**. +1. Select **Overview**** > ****Users**. 1. Use the search bar to find the locked user. 1. From the **User administration** dropdown list, select **Unlock**. diff --git a/doc/security/user_email_confirmation.md b/doc/security/user_email_confirmation.md index 25bd8a9c3d1c2c..ae652a193847cb 100644 --- a/doc/security/user_email_confirmation.md +++ b/doc/security/user_email_confirmation.md @@ -17,7 +17,7 @@ the user signs up. When this setting is enabled, the user is unable to sign in u they confirm their email address. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **General**. +1. Select **Settings**** > ****General**. 1. Expand **Sign-up restrictions** and look for the **Email confirmation settings** options. ## Confirmation token expiry diff --git a/doc/security/user_file_uploads.md b/doc/security/user_file_uploads.md index cb841d7b57b73c..ca8583e8e83786 100644 --- a/doc/security/user_file_uploads.md +++ b/doc/security/user_file_uploads.md @@ -64,7 +64,7 @@ Prerequisites: To configure authentication settings for all media files: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings** > **General**. +1. Select **Settings**** > ****General**. 1. Expand **Visibility, project features, permissions**. 1. Scroll to **Project visibility** and select **Require authentication to view media files**. diff --git a/doc/security/webhooks.md b/doc/security/webhooks.md index 0fe49e7e65ddfd..3203cf9143142d 100644 --- a/doc/security/webhooks.md +++ b/doc/security/webhooks.md @@ -56,7 +56,7 @@ To prevent exploitation of insecure internal web services, all webhook and integ To allow access to these addresses: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **Network**. +1. Select **Settings**** > ****Network**. 1. Expand **Outbound requests**. 1. Select the **Allow requests to the local network from webhooks and integrations** checkbox. @@ -69,7 +69,7 @@ Prerequisites: [System hooks](../administration/system_hooks.md) can make requests to the local network by default. To prevent system hook requests to the local network: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **Network**. +1. Select **Settings**** > ****Network**. 1. Expand **Outbound requests**. 1. Clear the **Allow requests to the local network from system hooks** checkbox. @@ -82,7 +82,7 @@ Prerequisites: [DNS rebinding](https://en.wikipedia.org/wiki/DNS_rebinding) is a technique to make a malicious domain name resolve to an internal network resource to bypass local network access restrictions. GitLab has protection against this attack enabled by default. To disable this protection: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **Network**. +1. Select **Settings**** > ****Network**. 1. Expand **Outbound requests**. 1. Clear the **Enforce DNS-rebinding attack protection** checkbox. @@ -101,7 +101,7 @@ Prerequisites: To filter requests by blocking many requests: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **Network**. +1. Select **Settings**** > ****Network**. 1. Expand **Outbound requests**. 1. Select the **Block all requests, except for IP addresses, IP ranges, and domain names defined in the allowlist** checkbox. @@ -124,7 +124,7 @@ Prerequisites: To allow outbound requests to certain IP addresses and domains: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **Network**. +1. Select **Settings**** > ****Network**. 1. Expand **Outbound requests**. 1. In **Local IP addresses and domain names that hooks and integrations can access**, enter your IP addresses and domains. diff --git a/doc/solutions/components/jira_dora.md b/doc/solutions/components/jira_dora.md index e9e72e6b86f5aa..0875c581a42400 100644 --- a/doc/solutions/components/jira_dora.md +++ b/doc/solutions/components/jira_dora.md @@ -64,7 +64,7 @@ Each incident creation counts as 1 run, and each incident resolution counts as 1 First we'll need to create an HTTP endpoint that can be triggered to create/resolve alerts in GitLab, which in turn create/resolve incidents. -1. Head to your GitLab project where you want Jira incidents to be created. From the sidebar, go to **Settings** > **Monitor**. Expand the **Alerts** section. +1. Head to your GitLab project where you want Jira incidents to be created. From the sidebar, go to **Settings**** > ****Monitor**. Expand the **Alerts** section. 1. Under **Alerts**, switch to the **Alert settings** tab. Check the following boxes, and click **Save changes**: - _Create an incident. Incidents are created for each alert triggered._ - _Automatically close associated incident when a recovery alert notification resolves an alert_ @@ -76,7 +76,7 @@ First we'll need to create an HTTP endpoint that can be triggered to create/reso To automatically trigger the GitLab alert endpoint when a Jira incident is created, we'll use [Jira automation](https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828). -1. Navigate to your Jira project where your incidents are managed. From the sidebar, head to **Project settings** > **Automation** (you may have to scroll down a bit to find it). +1. Navigate to your Jira project where your incidents are managed. From the sidebar, head to **Project settings**** > ****Automation** (you may have to scroll down a bit to find it). 1. From here we can manage our Jira automation workflows. At the top-right, click **Create rule**. 1. For your trigger, search for and select **Issue created**. Click **Save**. 1. Next, select **IF: Add a condition**. Here you can specify what conditions to check for, in order to determine if the issue created relates to an incident. For this guide, we'll select **Issue fields condition**. Under **Field**, we'll select **Summary**, the **Condition** will be set to **contains**, and the value will be `incident`. Click **Save**. @@ -108,7 +108,7 @@ Create another Jira automation workflow as described above, with the following c 1. Once you've created your Jira automation workflow, click on the workflow you just created, and select **Then: Send web request**. 1. Expand the **Validate your web request configuration** section, and enter a *resolved* issue key to test with (you must have an existing issue key that you can use). Click **Validate**. 1. Expand the **Request POST** section, and expand the **Payload** section. Copy the entire payload. -1. Head back into your GitLab project, and go to **Settings** > **Monitor** > **Alerts** > **Current Integrations**. Click the 'settings' icon next to the integration you created earlier, and switch to the **Configure details** tab. +1. Head back into your GitLab project, and go to **Settings**** > ****Monitor**** > ****Alerts**** > ****Current Integrations**. Click the 'settings' icon next to the integration you created earlier, and switch to the **Configure details** tab. 1. Under **Customize alert payload mapping**, paste the payload you copied from Jira in step 3. Then click **Parse payload fields**. 1. Map the fields as shown below: diff --git a/doc/solutions/components/jira_vsa.md b/doc/solutions/components/jira_vsa.md index 7a146fe530e2ab..fcff559cae986e 100644 --- a/doc/solutions/components/jira_vsa.md +++ b/doc/solutions/components/jira_vsa.md @@ -20,7 +20,7 @@ GitLab [Value Stream Analytics (VSA)](../../user/group/value_stream_analytics/_i For teams using Jira for issue tracking while leveraging GitLab for development, this integration enables automatic replication of Jira issues to GitLab in real-time. This ensures accurate VSA metrics without requiring teams to change their existing Jira workflows. -The integration also populates the GitLab **Value Streams Dashboard** (Ultimate only), which provides an overview of key DevSecOps metrics and can be found under **Analyze > Analytics dashboards** in your GitLab project or group. +The integration also populates the GitLab **Value Streams Dashboard** (Ultimate only), which provides an overview of key DevSecOps metrics and can be found under **Analyze** > **Analytics dashboards** in your GitLab project or group. **NOTE**: A similar integration exists for incident replication to generate specific DORA metrics (Change Failure Rate and Time to Restore Service). If you're interested in incident replication, refer to the [Jira Incident Replicator](jira_dora.md). @@ -64,7 +64,7 @@ Each issue creation counts as 1 run, and each issue resolution counts as 1 run. First, we need to create a GitLab project access token with the necessary permissions to create and update issues via the API. -1. Navigate to your GitLab project where you want Jira issues to be replicated. From the sidebar, go to **Settings > Access Tokens**. +1. Navigate to your GitLab project where you want Jira issues to be replicated. From the sidebar, go to **Settings** > **Access Tokens**. 1. Click **Add new token**. 1. Set the following configuration: - **Token name**: `Jira VSA Integration` (or any descriptive name) @@ -80,7 +80,7 @@ First, we need to create a GitLab project access token with the necessary permis To automatically create GitLab issues when Jira issues are created, we'll use [Jira automation](https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828). -1. Navigate to your Jira project. From the sidebar, head to **Project settings > Automation**. +1. Navigate to your Jira project. From the sidebar, head to **Project settings** > **Automation**. 1. Click **Create rule** at the top-right. 1. For your trigger, search for and select **Issue created**. Click **Save**. 1. *Optional*: Add conditions to filter which issues should be replicated. For example, you might want to add an **Issue fields condition** to only replicate issues of certain types or with specific labels. @@ -143,7 +143,7 @@ Once your automation workflows are active, GitLab will begin receiving issue dat The **Value Streams Dashboard** is automatically populated with metrics from your replicated issues and is available with GitLab Ultimate: -1. In your GitLab project or group, navigate to **Analyze > Analytics dashboards** +1. In your GitLab project or group, navigate to **Analyze** > **Analytics dashboards** 1. Click on **Value Streams Dashboard** 1. You'll see metrics including Issues created, Issues closed, Lead time, and Cycle time @@ -151,7 +151,7 @@ The **Value Streams Dashboard** is automatically populated with metrics from you For more detailed analytics and custom value streams (available with GitLab Premium and Ultimate): -1. Navigate to **Analyze > Value stream analytics** in your GitLab project or group +1. Navigate to **Analyze** > **Value stream analytics** in your GitLab project or group 1. Click **New value stream** to create a custom value stream 1. Configure stages and workflows according to your development process 1. Metrics like lead time and new issues count will be automatically generated and displayed next to the stages you create diff --git a/doc/solutions/components/oss_license_check.md b/doc/solutions/components/oss_license_check.md index c47b2f2c0564e0..2b349375625867 100644 --- a/doc/solutions/components/oss_license_check.md +++ b/doc/solutions/components/oss_license_check.md @@ -55,7 +55,7 @@ If you don't have a security policy project yet, you'll need to create one and t #### Setting up Dependency Scanning from scratch 1. First, identify which group you want to apply this policy to. This will be the highest group level where the policy can be applied (you can include or exclude projects within this group). -1. Navigate to that group's **Secure > Policies** page. +1. Navigate to that group's **Secure** > **Policies** page. 1. Click on **New policy**. 1. Select **Scan execution policy**. 1. Enter a name for your policy (for example, "Dependency Scanning Policy"). @@ -69,7 +69,7 @@ If you don't have a security policy project yet, you'll need to create one and t After setting up dependency scanning, follow these steps to set up the license compliance policy: -1. Navigate back to the same group's **Secure > Policies** page. +1. Navigate back to the same group's **Secure** > **Policies** page. 1. Click on **New policy**. 1. Select **Merge request approval policy**. 1. Enter a name for your policy (for example, "OSS Compliance Policy"). @@ -104,7 +104,7 @@ If you already have a security policy project but don't have dependency and/or l 1. Navigate to your group's Security policy project. 1. Navigate to the `policy.yml` file in `.gitlab/security-policies/`. -1. Click on **Edit** > **Edit single file**. +1. Click on **Edit**** > ****Edit single file**. 1. Add the `scan_execution_policy` and `approval_policy` sections from [Complete Policy Configuration](#complete-policy-configuration). 1. Make sure to: - Maintain the existing YAML structure diff --git a/doc/solutions/components/secret_detection.md b/doc/solutions/components/secret_detection.md index 9ef5c826f4bc1d..3da74beb360321 100644 --- a/doc/solutions/components/secret_detection.md +++ b/doc/solutions/components/secret_detection.md @@ -97,7 +97,7 @@ To run secret detection automatically in the pipeline as the enforced global pol set up the policy at the highest level (in this case, for the top-level group). To create the new secret detection policy: -1. Create the policy: In the same group `Secret Detection`, navigate to that group's **Secure > Policies** page. +1. Create the policy: In the same group `Secret Detection`, navigate to that group's **Secure** > **Policies** page. 1. Select **New policy**. 1. Select **Scan execution policy**. 1. Configure the policy: Give the policy name `Secret Detection Policy` and enter a description and select `Secret Detection` scan diff --git a/doc/solutions/components/securitykpi.md b/doc/solutions/components/securitykpi.md index 6aedfba70b1597..9a4a86dc4aa4ed 100644 --- a/doc/solutions/components/securitykpi.md +++ b/doc/solutions/components/securitykpi.md @@ -204,7 +204,7 @@ To set up the dashboard: 1. Save the provided `vuln_metrics_dashboard.xml` file. 1. In Splunk: 1. Go to the Search app. - 1. Click **Dashboards > Create New Dashboard**. + 1. Click **Dashboards** > **Create New Dashboard**. 1. Select **Source** in the edit view. 1. Replace the default XML with the contents of `vuln_metrics_dashboard.xml`. 1. Save the dashboard. diff --git a/doc/update/background_migrations.md b/doc/update/background_migrations.md index f8e76326cfc860..ea19af08d01771 100644 --- a/doc/update/background_migrations.md +++ b/doc/update/background_migrations.md @@ -81,7 +81,7 @@ Prerequisites: To check the status of batched background migrations: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Monitoring** > **Background migrations**. +1. Select **Monitoring**** > ****Background migrations**. 1. Select **Queued** or **Finalizing** to see incomplete migrations, and **Failed** for failed migrations. @@ -257,7 +257,7 @@ Prerequisites: - You must have administrator access to the instance. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Monitoring** > **Background migrations**. +1. Select **Monitoring**** > ****Background migrations**. 1. Select the **Failed** tab. This displays a list of failed batched background migrations. 1. Select the failed **Migration** to see the migration parameters and the jobs that failed. 1. Under **Failed jobs**, select each **ID** to see why the job failed. @@ -272,7 +272,7 @@ Prerequisites: - You must have administrator access to the instance. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Monitoring** > **Background migrations**. +1. Select **Monitoring**** > ****Background migrations**. 1. Select the **Failed** tab. This displays a list of failed batched background migrations. 1. Select a failed batched background migration to retry by clicking on the retry button ({{< icon name="retry" >}}). diff --git a/doc/user/application_security/api_fuzzing/_index.md b/doc/user/application_security/api_fuzzing/_index.md index 8de4aa2d445104..a5d34a783e4e1a 100644 --- a/doc/user/application_security/api_fuzzing/_index.md +++ b/doc/user/application_security/api_fuzzing/_index.md @@ -66,7 +66,7 @@ To enable API fuzzing: To view the output of a security scan: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Build > Pipelines**. +1. On the left sidebar, select **Build** > **Pipelines**. 1. Select the pipeline. 1. Select the **Security** tab. 1. Select a vulnerability to view its details, including: diff --git a/doc/user/application_security/api_fuzzing/configuration/enabling_the_analyzer.md b/doc/user/application_security/api_fuzzing/configuration/enabling_the_analyzer.md index 8a0c8e13941434..922043a1082df5 100644 --- a/doc/user/application_security/api_fuzzing/configuration/enabling_the_analyzer.md +++ b/doc/user/application_security/api_fuzzing/configuration/enabling_the_analyzer.md @@ -47,7 +47,7 @@ a YAML snippet that you can paste in your GitLab CI/CD configuration. To generate an API Fuzzing configuration snippet: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **API Fuzzing** row, select **Enable API Fuzzing**. 1. Complete the fields. For details see [Available CI/CD variables](variables.md). 1. Select **Generate code snippet**. @@ -890,7 +890,7 @@ Follow these steps to view details of a fuzzing fault: 1. You can view faults in a project, or a merge request: - - In a project, go to the project's **Secure > Vulnerability report** + - In a project, go to the project's **Secure** > **Vulnerability report** page. This page shows all vulnerabilities from the default branch only. - In a merge request, go the merge request's **Security** section and select the **Expand** button. API Fuzzing faults are available in a section labeled diff --git a/doc/user/application_security/api_fuzzing/create_har_files.md b/doc/user/application_security/api_fuzzing/create_har_files.md index 5470a2c802967a..7f7878187bc4be 100644 --- a/doc/user/application_security/api_fuzzing/create_har_files.md +++ b/doc/user/application_security/api_fuzzing/create_har_files.md @@ -99,7 +99,7 @@ used in [Web API Fuzz Testing](configuration/enabling_the_analyzer.md#http-archi 1. Verify each API call works. - If you imported an OpenAPI specification, go through and add working data. 1. Select **API > Import/Export**. -1. Select **Export Data > Current Workspace**. +1. Select **Export Data** > **Current Workspace**. 1. Select requests to include in the HAR file. 1. Select **Export**. 1. In the **Select Export Type** dropdown list select **HAR -- HTTP Archive Format**. @@ -117,7 +117,7 @@ responses in HAR format. 1. Go to the [Fiddler home page](https://www.telerik.com/fiddler) and sign in. If you don't already have an account, first create an account. 1. Browse pages that call an API. Fiddler automatically captures the requests. -1. Select one or more requests, then from the context menu, select **Export > Selected Sessions**. +1. Select one or more requests, then from the context menu, select **Export** > **Selected Sessions**. 1. In the **Choose Format** dropdown list select **HTTPArchive v1.2**. 1. Enter a filename and select **Save**. @@ -135,12 +135,12 @@ Prerequisites: - Enable the `Develop` menu item. 1. Open Safari's preferences. Press Command+, or from the menu, select - **Safari > Preferences**. + **Safari** > **Preferences**. 1. Select **Advanced** tab, then select `Show Develop menu item in menu bar`. 1. Close the **Preferences** window. 1. Open the **Web Inspector**. Press Option+Command+i, or from the - menu, select **Develop > Show Web Inspector**. + menu, select **Develop** > **Show Web Inspector**. 1. Select the **Network** tab, and select **Preserve Log**. 1. Browse pages that call the API. 1. Open the **Web Inspector** and select the **Network** tab diff --git a/doc/user/application_security/api_security_testing/_index.md b/doc/user/application_security/api_security_testing/_index.md index 08197a08057ab8..3b07c39639aaa8 100644 --- a/doc/user/application_security/api_security_testing/_index.md +++ b/doc/user/application_security/api_security_testing/_index.md @@ -82,7 +82,7 @@ To enable API security testing, you must alter your GitLab CI/CD configuration Y To view the output of a security scan: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Build > Pipelines**. +1. On the left sidebar, select **Build** > **Pipelines**. 1. Select the pipeline. 1. Select the **Security** tab. 1. Select a vulnerability to view its details, including: diff --git a/doc/user/application_security/api_security_testing/configuration/enabling_the_analyzer.md b/doc/user/application_security/api_security_testing/configuration/enabling_the_analyzer.md index 741fd7ff005c4b..fdd129da0cba35 100644 --- a/doc/user/application_security/api_security_testing/configuration/enabling_the_analyzer.md +++ b/doc/user/application_security/api_security_testing/configuration/enabling_the_analyzer.md @@ -804,7 +804,7 @@ Follow these steps to view details of a vulnerability: 1. You can view vulnerabilities in a project, or a merge request: - - In a project, go to the project's **Secure > Vulnerability report** + - In a project, go to the project's **Secure** > **Vulnerability report** page. This page shows all vulnerabilities from the default branch only. - In a merge request, go the merge request's **Security** section and select the **Expand** button. API security testing vulnerabilities are available in a section labeled diff --git a/doc/user/application_security/container_scanning/_index.md b/doc/user/application_security/container_scanning/_index.md index e3df38aa465312..afaf9a5c31b448 100644 --- a/doc/user/application_security/container_scanning/_index.md +++ b/doc/user/application_security/container_scanning/_index.md @@ -115,7 +115,7 @@ might occur. In that case, use the [manual](#edit-the-gitlab-ciyml-file-manually To enable Container Scanning: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Container Scanning** row, select **Configure with a merge request**. 1. Select **Create merge request**. 1. Review the merge request, then select **Merge**. @@ -130,7 +130,7 @@ your GitLab CI/CD configuration file is complex or you need to use non-default o To enable Container Scanning: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline editor**. +1. Select **Build** > **Pipeline editor**. 1. If no `.gitlab-ci.yml` file exists, select **Configure pipeline**, then delete the example content. 1. Copy and paste the following to the bottom of the `.gitlab-ci.yml` file. If an `include` line @@ -159,7 +159,7 @@ Pipelines now include a Container Scanning job. You can review vulnerabilities in a pipeline: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Build > Pipelines**. +1. On the left sidebar, select **Build** > **Pipelines**. 1. Select the pipeline. 1. Select the **Security** tab. 1. Select a vulnerability to view its details, including: @@ -936,7 +936,7 @@ Container Scanning for Registry populates the vulnerability report only when a n To enable container scanning for the GitLab Container Registry: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. Scroll down to the **Container Scanning For Registry** section and turn on the toggle. ## Vulnerabilities database diff --git a/doc/user/application_security/coverage_fuzzing/_index.md b/doc/user/application_security/coverage_fuzzing/_index.md index ab48f09cab1041..55134f39c3f31f 100644 --- a/doc/user/application_security/coverage_fuzzing/_index.md +++ b/doc/user/application_security/coverage_fuzzing/_index.md @@ -32,7 +32,7 @@ For an overview, see [Coverage Fuzzing](https://www.youtube.com/watch?v=bbIenVVc To confirm the status of coverage-guided fuzz testing: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Coverage Fuzzing** section the status is: - **Not configured** - **Enabled** @@ -121,7 +121,7 @@ artifacts files you can download from the CI/CD pipeline. Also, a project member To view details of the corpus registry: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Coverage Fuzzing** section, select **Manage corpus**. #### Create a corpus in the corpus registry @@ -149,7 +149,7 @@ provided by the `COVFUZZ_CORPUS_NAME` variable. The corpus is updated on every p To upload an existing corpus file: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Coverage Fuzzing** section, select **Manage corpus**. 1. Select **New corpus**. 1. Complete the fields. diff --git a/doc/user/application_security/dast/browser/_index.md b/doc/user/application_security/dast/browser/_index.md index 86b04cae91d484..d78cf3e385159c 100644 --- a/doc/user/application_security/dast/browser/_index.md +++ b/doc/user/application_security/dast/browser/_index.md @@ -89,7 +89,7 @@ To enable DAST in a project: You can review vulnerabilities in a pipeline: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Build > Pipelines**. +1. On the left sidebar, select **Build** > **Pipelines**. 1. Select the pipeline. 1. Select the **Security** tab. 1. Select a vulnerability to view its details, including: diff --git a/doc/user/application_security/dast/profiles.md b/doc/user/application_security/dast/profiles.md index c83c3c71f3870b..f333114187b06f 100644 --- a/doc/user/application_security/dast/profiles.md +++ b/doc/user/application_security/dast/profiles.md @@ -98,9 +98,9 @@ Each of the site validation methods are equivalent in functionality, so use whic To create a site profile: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**. -1. Select **New > Site profile**. +1. Select **New** > **Site profile**. 1. Complete the fields then select **Save profile**. The site profile is saved, for use in an on-demand scan. @@ -129,7 +129,7 @@ When a validated site profile's file, header, or meta tag is edited, the site's To edit a site profile: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**. 1. Select the **Site Profiles** tab. 1. In the profile's row select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Edit**. @@ -151,7 +151,7 @@ See [Scan execution policies](../policies/scan_execution_policies.md) for more i To delete a site profile: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**. 1. Select the **Site Profiles** tab. 1. In the profile's row, select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Delete**. @@ -168,7 +168,7 @@ Prerequisites: To validate a site profile: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**. 1. Select the **Site Profiles** tab. 1. In the profile's row, select **Validate**. @@ -201,7 +201,7 @@ page. To retry a site profile's failed validation: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**. 1. Select the **Site Profiles** tab. 1. In the profile's row, select **Retry validation**. @@ -218,7 +218,7 @@ have their validation status revoked. To revoke a site profile's validation status: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**. 1. Beside the validated profile, select **Revoke validation**. @@ -310,9 +310,9 @@ dast: To create a scanner profile: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**. -1. Select **New > Scanner profile**. +1. Select **New** > **Scanner profile**. 1. Complete the form. For details of each field, see [Scanner profile](#scanner-profile). 1. Select **Save profile**. @@ -332,7 +332,7 @@ For more information, see [Scan execution policies](../policies/scan_execution_p To edit a scanner profile: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**. 1. Select the **Scanner profiles** tab. 1. In the scanner's row, select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Edit**. @@ -355,7 +355,7 @@ page. For more information, see [Scan execution policies](../policies/scan_execu To delete a scanner profile: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Dynamic Application Security Testing (DAST)** section, select **Manage profiles**. 1. Select the **Scanner profiles** tab. 1. In the scanner's row, select the **More actions** ({{< icon name="ellipsis_v" >}}) menu, then select **Delete**. diff --git a/doc/user/application_security/dependency_list/_index.md b/doc/user/application_security/dependency_list/_index.md index 859fe43d0e68ee..af9dd4c46f61c9 100644 --- a/doc/user/application_security/dependency_list/_index.md +++ b/doc/user/application_security/dependency_list/_index.md @@ -68,7 +68,7 @@ For more information, see the history. To view the dependencies of a project or all projects in a group: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Dependency list**. +1. Select **Secure** > **Dependency list**. 1. Optional. If there are transitive dependencies, you can also view all of the dependency paths: - For a project, in the **Location** column, select **View dependency paths**. - For a group, in the **Location** column, select the location, then select **View dependency paths**. @@ -117,7 +117,7 @@ To filter by component version, you must filter by exactly one component first. To filter the dependency list: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Dependency list**. +1. Select **Secure** > **Dependency list**. 1. Select the filter bar. 1. Select a filter, then from the dropdown list select one or more criteria. To close the dropdown list, select outside of it. To add more filters, repeat this step. @@ -197,7 +197,7 @@ You can export the dependency list in: To download the dependency list: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Dependency list**. +1. Select **Secure** > **Dependency list**. 1. Select **Export** and then select the file format. When the exported details are available, you'll receive an email. To download the exported details, select the link in the email. diff --git a/doc/user/application_security/dependency_scanning/_index.md b/doc/user/application_security/dependency_scanning/_index.md index 3179ec15d3e261..562b568e6f3a8d 100644 --- a/doc/user/application_security/dependency_scanning/_index.md +++ b/doc/user/application_security/dependency_scanning/_index.md @@ -130,7 +130,7 @@ might occur. In that case, use the [manual](#edit-the-gitlab-ciyml-file-manually To enable Dependency Scanning: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Dependency Scanning** row, select **Configure with a merge request**. 1. Select **Create merge request**. 1. Review the merge request, then select **Merge**. @@ -145,7 +145,7 @@ your GitLab CI/CD configuration file is complex. To enable Dependency Scanning: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline editor**. +1. Select **Build** > **Pipeline editor**. 1. If no `.gitlab-ci.yml` file exists, select **Configure pipeline**, then delete the example content. 1. Copy and paste the following to the bottom of the `.gitlab-ci.yml` file. If an `include` line @@ -195,7 +195,7 @@ After completing these steps, you can: You can review vulnerabilities in a pipeline: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Build > Pipelines**. +1. On the left sidebar, select **Build** > **Pipelines**. 1. Select the pipeline. 1. Select the **Security** tab. 1. Select a vulnerability to view its details, including: @@ -1534,7 +1534,7 @@ Follow these best practices when you build projects that use CocoaPods for depen 1. Open your `.xcworkspace` file in Xcode. 1. Select your target scheme. - 1. Select **Product > Build**. You can also press ⌘+B. + 1. Select **Product** > **Build**. You can also press ⌘+B. - [fastlane](https://fastlane.tools/), a tool for automating builds and releases for iOS and Android apps: diff --git a/doc/user/application_security/detect/roll_out_security_scanning.md b/doc/user/application_security/detect/roll_out_security_scanning.md index f7bedac08d3e1f..a05dcf52c64e80 100644 --- a/doc/user/application_security/detect/roll_out_security_scanning.md +++ b/doc/user/application_security/detect/roll_out_security_scanning.md @@ -157,7 +157,7 @@ Prerequisites: For each project in scope: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. Expand **Security configuration**. 1. Enable the appropriate application security testing based on your project's stack. @@ -172,7 +172,7 @@ Introduce developers to the tools that provide visibility into security findings Developers can view security findings directly in pipeline results: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. Select the pipeline to review. 1. In the pipeline details, select the **Security** tab to view detected vulnerabilities. @@ -256,7 +256,7 @@ review from a member of the application security team, providing an extra level Configure approval policies to require security reviews: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Policies**. +1. Select **Secure** > **Policies**. 1. Select **New policy** 1. In the **Merge request approval policy** pane, select **Select policy**. 1. Add a merge request approval policy requiring approval from security team members. @@ -343,7 +343,7 @@ Prerequisites: the groups in which application security testing is to be enabled. 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Policies**. +1. Select **Secure** > **Policies**. 1. Create scan execution policies based on the application security testing configuration used during the pilot phase. diff --git a/doc/user/application_security/detect/security_configuration.md b/doc/user/application_security/detect/security_configuration.md index eac935dc65fb82..36848543ed7d7b 100644 --- a/doc/user/application_security/detect/security_configuration.md +++ b/doc/user/application_security/detect/security_configuration.md @@ -80,7 +80,7 @@ default branch. To view a project's security configuration: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. To see a historic view of changes to the CI/CD configuration file, select **Configuration history**. @@ -89,7 +89,7 @@ To see a historic view of changes to the CI/CD configuration file, select **Conf To edit a project's security configuration: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. Select the security scanner you want to enable or configure and follow the instructions. For more details on how to enable and configure individual security scanners, see their diff --git a/doc/user/application_security/detect/security_scanning_results.md b/doc/user/application_security/detect/security_scanning_results.md index 08540ca3baf75f..bc7344615f427a 100644 --- a/doc/user/application_security/detect/security_scanning_results.md +++ b/doc/user/application_security/detect/security_scanning_results.md @@ -76,7 +76,7 @@ purposes. A security report is a JSON file. To download a security report: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. Select the pipeline. 1. Select the **Security** tab. 1. Select **Download results**, then the desired security report. @@ -113,7 +113,7 @@ branch. To view a pipeline security report: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. Select the latest pipeline. To see details of a finding or vulnerability, select its description. @@ -132,7 +132,7 @@ Prerequisites: To change the status and severity of findings or vulnerabilities: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. Select the latest pipeline. 1. Select the **Security** tab. 1. In the finding report: @@ -151,7 +151,7 @@ To change the status and severity of findings or vulnerabilities: Create an issue to track, document, and manage the remediation work for a finding or vulnerability. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. Select the pipeline. 1. Select the **Security** tab. 1. Select a finding's description. diff --git a/doc/user/application_security/iac_scanning/_index.md b/doc/user/application_security/iac_scanning/_index.md index 8fc15581740bd6..3089d2b5436cf1 100644 --- a/doc/user/application_security/iac_scanning/_index.md +++ b/doc/user/application_security/iac_scanning/_index.md @@ -79,7 +79,7 @@ After completing these steps, you can: You can review vulnerabilities in a pipeline: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Build > Pipelines**. +1. On the left sidebar, select **Build** > **Pipelines**. 1. Select the pipeline. 1. Select the **Security** tab. 1. Select a vulnerability to view its details, including: @@ -319,7 +319,7 @@ For example, you might need to avoid a regression in a later release. To use a specific analyzer version: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline editor**. +1. Select **Build** > **Pipeline editor**. 1. Add the `SAST_ANALYZER_IMAGE_TAG` CI/CD variable, after the line that includes the `SAST-IaC.gitlab-ci.yml` template. diff --git a/doc/user/application_security/policies/_index.md b/doc/user/application_security/policies/_index.md index c382022c89a1f0..c16aaa4e6f41a6 100644 --- a/doc/user/application_security/policies/_index.md +++ b/doc/user/application_security/policies/_index.md @@ -303,7 +303,7 @@ policy's information (for example, description or enforcement status), and creat policies: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Policies**. +1. Select **Secure** > **Policies**. ![Policies List Page](img/policies_list_v17_7.png) @@ -314,7 +314,7 @@ A green checkmark in the first column indicates that the policy is enabled and e Use the policy editor to create, edit, and delete policies: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Policies**. +1. Select **Secure** > **Policies**. - To create a new policy, select **New policy** which is located in the **Policies** page's header. You can then select which type of policy to create. - To edit an existing policy, select **Edit policy** in the selected policy drawer. diff --git a/doc/user/application_security/policies/centralized_security_policy_management.md b/doc/user/application_security/policies/centralized_security_policy_management.md index c4384dfd7d82df..d718ae4fbc008c 100644 --- a/doc/user/application_security/policies/centralized_security_policy_management.md +++ b/doc/user/application_security/policies/centralized_security_policy_management.md @@ -68,7 +68,7 @@ To support approval groups globally across your instance, you must: To create the policies: 1. Go to your designated CSP group. -1. Go to **Secure** > **Policies**. +1. Go to **Secure**** > ****Policies**. 1. Create one or more security policies as you typically would. Before you save each policy: - In the **Policy scope** section, select a scope to apply the policy to: - **Groups**: Apply the policy to specific groups and subgroups. @@ -85,8 +85,8 @@ CSP policies are stored in a `policy.yml` file in the designated CSP group, simi - Depending on the number of groups and projects in scope, policy changes may take some time to apply across your instance. - The synchronization process uses background jobs that are automatically queued when you designate a CSP group, create policies, or update policies. -- Instance administrators can monitor background job processing in **Admin Area** > **Monitoring** > **Background jobs**. -- To verify that policies are successfully applied in a target group or project, go to **Secure** > **Policies** in the group or project. +- Instance administrators can monitor background job processing in **Admin Area**** > ****Monitoring**** > ****Background jobs**. +- To verify that policies are successfully applied in a target group or project, go to **Secure**** > ****Policies** in the group or project. ## Troubleshooting diff --git a/doc/user/application_security/policies/merge_request_approval_policies.md b/doc/user/application_security/policies/merge_request_approval_policies.md index 00176f489b1b80..fbfaa847d34db7 100644 --- a/doc/user/application_security/policies/merge_request_approval_policies.md +++ b/doc/user/application_security/policies/merge_request_approval_policies.md @@ -541,12 +541,12 @@ For a video walkthrough, see [Security policies: Recreate a pipeline execution p To recreate a pipeline execution policy: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Policies**. +1. Select **Secure** > **Policies**. 1. Select the pipeline execution policy you want to recreate. 1. On the right sidebar, select the **YAML** tab and copy the contents of the entire policy file. 1. Next to the policies table, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}), and select **Delete**. 1. Merge the generated merge request. -1. Go back to **Secure > Policies** and select **New policy**. +1. Go back to **Secure** > **Policies** and select **New policy**. 1. In the **Pipeline execution policy** section, select **Select policy**. 1. In the **.YAML mode**, paste the contents of the old policy. 1. Select **Update via merge request** and merge the generated merge request. diff --git a/doc/user/application_security/policies/pipeline_execution_policies.md b/doc/user/application_security/policies/pipeline_execution_policies.md index f7aa4eb3c66c25..c446da4b71d7ee 100644 --- a/doc/user/application_security/policies/pipeline_execution_policies.md +++ b/doc/user/application_security/policies/pipeline_execution_policies.md @@ -330,7 +330,7 @@ The *Maximum 5 pipeline execution policies per security policy project* limit ca On GitLab Self-Managed instances, administrators can adjust the limits for the entire instance, up to a maximum of 20 pipeline execution policies: -1. Go to **Admin Area** > **Settings** > **Security and compliance**. +1. Go to **Admin Area**** > ****Settings**** > ****Security and compliance**. 1. Expand the **Security policies** section. 1. Set a new value for **Maximum number of pipeline execution policies allowed per security policy configuration**. 1. Select **Save changes**. @@ -345,7 +345,7 @@ Increasing these limits can affect system performance, especially for complex po To adjust the limit for a top-level group: -1. Go to **Admin Area** > **Overview** > **Groups**. +1. Go to **Admin Area**** > ****Overview**** > ****Groups**. 1. In the row of the top-level group you want to modify, select **Edit**. 1. Set a new value for **Maximum number of pipeline execution policies allowed per security policy configuration**. 1. Select **Save changes**. @@ -372,7 +372,7 @@ Prerequisites: If you don't yet have a security policy project and you want to create the first pipeline execution policy, create an empty project and link it as a security policy project. To link the project: -1. In the group or project where you want to enforce the policy, select **Secure** > **Policies** > **Edit policy project**. +1. In the group or project where you want to enforce the policy, select **Secure**** > ****Policies**** > ****Edit policy project**. 1. Select the security policy project. The project becomes a security policy project, and the setting becomes available. @@ -387,7 +387,7 @@ If you don't see the **CI/CD** settings, go to **Settings > General > Visibility #### Configuration -1. In the policy project, select **Settings** > **General** > **Visibility, project features, permissions**. +1. In the policy project, select **Settings**** > ****General**** > ****Visibility, project features, permissions**. 1. Enable the setting **Pipeline execution policies: Grant access to the CI/CD configurations for projects linked to this security policy project as the source for security policies**. 1. In the policy project, create a file for the policy CI/CD configuration. diff --git a/doc/user/application_security/policies/scheduled_pipeline_execution_policies.md b/doc/user/application_security/policies/scheduled_pipeline_execution_policies.md index 5e39e13ab4f3a5..9f39b727e5fdcb 100644 --- a/doc/user/application_security/policies/scheduled_pipeline_execution_policies.md +++ b/doc/user/application_security/policies/scheduled_pipeline_execution_policies.md @@ -256,7 +256,7 @@ In this example, if all of the specified branches exist in the project, the poli To use scheduled pipeline execution policies: 1. Store your CI/CD configuration in your security policy project. -1. In your security policy project's **Settings** > **General** > **Visibility, project features, permissions** section, enable the **Grant security policy project access to CI/CD configuration** setting. +1. In your security policy project's **Settings**** > ****General**** > ****Visibility, project features, permissions** section, enable the **Grant security policy project access to CI/CD configuration** setting. 1. Ensure your CI/CD configuration includes appropriate workflow rules for scheduled pipelines. The security policy bot is a system account that GitLab automatically creates to handle the execution of security policies. When you enable the appropriate settings, this bot is granted the necessary permissions to access CI/CD configurations and run scheduled pipelines. The permissions are only necessary if the CI/CD configurations is not in a public project. @@ -277,7 +277,7 @@ If your scheduled pipelines are not running as expected, follow these troublesho 1. **Verify experimental flag**: Ensure that the `pipeline_execution_schedule_policy: enabled: true` flag is set in the `experiments` section of your `policy.yml` file. 1. **Check policy access**: Verify that your security policy project has access to the CI/CD configuration: - - Go to the security policy project's **Settings** > **General** > **Visibility, project features, permissions** and ensure the "Pipeline execution policies" setting is enabled. + - Go to the security policy project's **Settings**** > ****General**** > ****Visibility, project features, permissions** and ensure the "Pipeline execution policies" setting is enabled. 1. **Validate CI configuration**: - Check that the CI/CD configuration file exists at the specified path. - Verify the configuration is valid by running a manual pipeline. diff --git a/doc/user/application_security/policies/security_policy_projects.md b/doc/user/application_security/policies/security_policy_projects.md index caae73725c1181..bc4fc9214c9fa7 100644 --- a/doc/user/application_security/policies/security_policy_projects.md +++ b/doc/user/application_security/policies/security_policy_projects.md @@ -157,7 +157,7 @@ Prerequisites: To link a group, subgroup, or project to a security policy project: 1. On the left sidebar, select **Search or go to** and find your project, subgroup, or group. -1. Select **Secure > Policies**. +1. Select **Secure** > **Policies**. 1. Select **Edit Policy Project**, then search for and select the project you would like to link from the dropdown list. 1. Select **Save**. diff --git a/doc/user/application_security/policies/vulnerability_management_policy.md b/doc/user/application_security/policies/vulnerability_management_policy.md index 4b4aa5cbe50676..b434ad62ad35d1 100644 --- a/doc/user/application_security/policies/vulnerability_management_policy.md +++ b/doc/user/application_security/policies/vulnerability_management_policy.md @@ -69,7 +69,7 @@ Prerequisites: To create a vulnerability management policy: 1. On the left sidebar, select **Search or go to** and find your project. -1. Go to **Secure > Policies**. +1. Go to **Secure** > **Policies**. 1. Select **New policy**. 1. In **Vulnerability management policy**, select **Select policy**. 1. Complete the fields and set the policy's status to **Enabled**. @@ -84,7 +84,7 @@ pipelines on the default branch. Edit a vulnerability management policy to change its rules. 1. On the left sidebar, select **Search or go to** and find your project. -1. Go to **Secure > Policies**. +1. Go to **Secure** > **Policies**. 1. In the policy's row, select **Edit**. 1. Edit the policy's details. 1. Select **Save changes**. diff --git a/doc/user/application_security/sast/_index.md b/doc/user/application_security/sast/_index.md index 42b92de987d1cc..a13e5d577469a8 100644 --- a/doc/user/application_security/sast/_index.md +++ b/doc/user/application_security/sast/_index.md @@ -129,7 +129,7 @@ After completing these steps, you can: You can review vulnerabilities in a pipeline: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Build > Pipelines**. +1. On the left sidebar, select **Build** > **Pipelines**. 1. Select the pipeline. 1. Select the **Security** tab. 1. Select a vulnerability to view its details, including: @@ -482,7 +482,7 @@ successfully, and an error may occur. To enable and configure SAST with customizations: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. If the latest pipeline for the default branch of the project has completed and produced valid `SAST` artifacts, select **Configure SAST**, otherwise select **Enable SAST** in the Static Application Security Testing (SAST) row. @@ -508,7 +508,7 @@ successfully, and an error may occur. To enable and configure SAST with default settings: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the SAST section, select **Configure with a merge request**. 1. Review and merge the merge request to enable SAST. diff --git a/doc/user/application_security/sast/gitlab_advanced_sast.md b/doc/user/application_security/sast/gitlab_advanced_sast.md index 6368416bf4254c..46075ea8e4d49d 100644 --- a/doc/user/application_security/sast/gitlab_advanced_sast.md +++ b/doc/user/application_security/sast/gitlab_advanced_sast.md @@ -184,7 +184,7 @@ You can set this variable by: To enable GitLab Advanced SAST by using the pipeline editor: -1. In your project, select **Build > Pipeline editor**. +1. In your project, select **Build** > **Pipeline editor**. 1. If no `.gitlab-ci.yml` file exists, select **Configure pipeline**, then delete the example content. 1. Update the CI/CD configuration to: @@ -304,7 +304,7 @@ expected, reach out to GitLab Support for further assistance with the following To identify the GitLab Advanced SAST analyzer version: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Jobs**. +1. Select **Build** > **Jobs**. 1. Locate the `gitlab-advanced-sast` job. 1. In the output of the job, search for the string `GitLab GitLab Advanced SAST analyzer`. diff --git a/doc/user/application_security/secret_detection/exclusions.md b/doc/user/application_security/secret_detection/exclusions.md index 685be622674592..0d90d12a425614 100644 --- a/doc/user/application_security/secret_detection/exclusions.md +++ b/doc/user/application_security/secret_detection/exclusions.md @@ -60,7 +60,7 @@ Prerequisites: To define an exclusion: 1. In the left sidebar, select **Search or go to** and go to your project or group. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. Scroll down to **Secret push protection**. 1. Turn on the **Secret push protection** toggle. 1. Select **Configure Secret Detection** ({{< icon name="settings" >}}). diff --git a/doc/user/application_security/secret_detection/pipeline/_index.md b/doc/user/application_security/secret_detection/pipeline/_index.md index 33864110e0873c..ed14f7724dadd6 100644 --- a/doc/user/application_security/secret_detection/pipeline/_index.md +++ b/doc/user/application_security/secret_detection/pipeline/_index.md @@ -77,7 +77,7 @@ After you enable pipeline secret detection, you can [customize the analyzer sett This method requires you to manually edit an existing `.gitlab-ci.yml` file. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipeline editor**. +1. Select **Build** > **Pipeline editor**. 1. Copy and paste the following to the bottom of the `.gitlab-ci.yml` file: ```yaml @@ -102,7 +102,7 @@ This method automatically prepares a merge request to add a `.gitlab-ci.yml` fil To enable pipeline secret detection: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. In the **Pipeline secret detection** row, select **Configure with a merge request**. 1. Optional. Complete the fields. 1. Select **Create merge request**. @@ -150,7 +150,7 @@ by default the first scheduled scan is a historic scan. To run a historic scan: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Pipelines**. +1. Select **Build** > **Pipelines**. 1. Select **New pipeline**. 1. Add a CI/CD variable: 1. From the dropdown list, select **Variable**. diff --git a/doc/user/application_security/secret_detection/push_protection_tutorial.md b/doc/user/application_security/secret_detection/push_protection_tutorial.md index ff551922ef425b..22fba1efd9388d 100644 --- a/doc/user/application_security/secret_detection/push_protection_tutorial.md +++ b/doc/user/application_security/secret_detection/push_protection_tutorial.md @@ -45,7 +45,7 @@ To use secret push protection, you need to enable it for each project you want t Let's start by enabling it in a test project. 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Secure > Security configuration**. +1. On the left sidebar, select **Secure** > **Security configuration**. 1. Turn on the **Secret push protection** toggle. Next, you'll test secret push protection. diff --git a/doc/user/application_security/secret_detection/secret_push_protection/_index.md b/doc/user/application_security/secret_detection/secret_push_protection/_index.md index 150d45a5ad6ee2..d1dc8a970ef813 100644 --- a/doc/user/application_security/secret_detection/secret_push_protection/_index.md +++ b/doc/user/application_security/secret_detection/secret_push_protection/_index.md @@ -90,7 +90,7 @@ To allow the use of secret push protection in your GitLab instance: 1. Sign in to your GitLab instance as an administrator. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Security and compliance**. +1. Select **Settings** > **Security and compliance**. 1. Under **Secret detection**, select or clear **Allow secret push protection**. Secret push protection is allowed on the instance. To use this feature, you must enable it per project. @@ -105,7 +105,7 @@ Prerequisites: To enable secret push protection in a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Secure > Security configuration**. +1. On the left sidebar, select **Secure** > **Security configuration**. 1. Turn on the **Secret push protection** toggle. You can also enable secret push protection for all projects in a group [with the API](../../../../api/group_security_settings.md#update-secret_push_protection_enabled-setting). diff --git a/doc/user/application_security/security_dashboard/_index.md b/doc/user/application_security/security_dashboard/_index.md index a596b4dcc657da..9f64be57215d65 100644 --- a/doc/user/application_security/security_dashboard/_index.md +++ b/doc/user/application_security/security_dashboard/_index.md @@ -66,7 +66,7 @@ with up to 365 days of historical data for a given project. The dashboard is a h To view a project's security dashboard: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security dashboard**. +1. Select **Secure** > **Security dashboard**. 1. Filter and search for what you need. - To filter the chart by severity, select the legend name. - To view a specific time frame, use the time range handles ({{< icon name="scroll-handle" >}}). @@ -83,7 +83,7 @@ to use in documentation, presentations, and so on. To download the image of the chart: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security dashboard**. +1. Select **Secure** > **Security dashboard**. 1. Select **Save chart as an image** ({{< icon name="download" >}}). You will then be prompted to download the image in SVG format. @@ -108,7 +108,7 @@ supplies the following: To view group security dashboard: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Security > Security dashboard**. +1. Select **Security** > **Security dashboard**. 1. Hover over the **Vulnerabilities over time** chart to get more details about vulnerabilities. - You can display the vulnerability trends over a 30, 60, or 90-day time frame (the default is 90 days). - To view aggregated data beyond a 90-day time frame, use the [VulnerabilitiesCountByDay GraphQL API](../../../api/graphql/reference/_index.md#vulnerabilitiescountbyday). GitLab retains the data for 365 days. @@ -138,7 +138,7 @@ To view the Security Center: 1. On the left sidebar, select **Search or go to**. 1. Select **Your work**. -1. Select **Security > Security dashboard**. +1. Select **Security** > **Security dashboard**. The Security Center is blank by default. You must add a project which have been configured with at least one security scanner. diff --git a/doc/user/application_security/security_inventory/_index.md b/doc/user/application_security/security_inventory/_index.md index 17e952f12304bb..c3f8db74feb2f5 100644 --- a/doc/user/application_security/security_inventory/_index.md +++ b/doc/user/application_security/security_inventory/_index.md @@ -55,7 +55,7 @@ Prerequisites: To view the security inventory: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Security inventory**. +1. Select **Secure** > **Security inventory**. 1. Select a group to view its subgroups, projects, and security assets. ## Related topics diff --git a/doc/user/application_security/vulnerabilities/_index.md b/doc/user/application_security/vulnerabilities/_index.md index 5c920b28f579c6..1286eeb4b5f464 100644 --- a/doc/user/application_security/vulnerabilities/_index.md +++ b/doc/user/application_security/vulnerabilities/_index.md @@ -78,7 +78,7 @@ Prerequisites: To explain the vulnerability: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Optional. To remove the default filters, select **Clear** ({{< icon name="clear" >}}). 1. Above the list of vulnerabilities, select the filter bar. 1. In the dropdown list that appears, select **Tool**, then select all the values in the **SAST** category. @@ -150,7 +150,7 @@ Learn more about [how to enable all GitLab Duo features](../../ai_features_enabl To resolve the vulnerability: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Optional. To remove the default filters, select **Clear** ({{< icon name="clear" >}}). 1. Above the list of vulnerabilities, select the filter bar. 1. In the dropdown list that appears, select **Activity**, then select **Vulnerability Resolution available** in the **GitLab Duo (AI)** category. @@ -407,7 +407,7 @@ Prerequisites: To change a vulnerability's status from its Vulnerability Page: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Select the vulnerability's description. 1. Select **Change status**. 1. From the **Status** dropdown list, select a status or a [dismissal reason](#vulnerability-dismissal-reasons) @@ -423,7 +423,7 @@ You can create a GitLab issue to track any action taken to resolve or mitigate a To create a GitLab issue for a vulnerability: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Select the vulnerability's description. 1. Select **Create issue**. @@ -446,7 +446,7 @@ Prerequisites: To link a vulnerability to existing GitLab issues: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Select the vulnerability's description. 1. In the **Linked issues** section, select the plus icon ({{< icon name="plus" >}}). 1. For each issue to be linked, either: @@ -522,7 +522,7 @@ To resolve a vulnerability, you can either: To resolve the vulnerability with a merge request: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Select the vulnerability's description. 1. From the **Resolve with merge request** dropdown list, select **Resolve with merge request**. @@ -534,7 +534,7 @@ Process the merge request according to your standard workflow. To manually apply the patch that GitLab generated for a vulnerability: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Select the vulnerability's description. 1. From the **Resolve with merge request** dropdown list, select **Download patch to resolve**. 1. Ensure your local project has the same commit checked out that was used to generate the patch. @@ -558,7 +558,7 @@ Security training helps your developers learn how to fix vulnerabilities. Develo To enable security training for vulnerabilities in your project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Security configuration**. +1. Select **Secure** > **Security configuration**. 1. On the tab bar, select **Vulnerability Management**. 1. To enable a security training provider, turn on the toggle. @@ -576,7 +576,7 @@ Vulnerabilities with a CWE are most likely to return a training result. To view the security training for a vulnerability: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Select the vulnerability for which you want to view security training. 1. Select **View training**. diff --git a/doc/user/application_security/vulnerability_archival/_index.md b/doc/user/application_security/vulnerability_archival/_index.md index 9829debf7fa118..57331c4a8a1b5c 100644 --- a/doc/user/application_security/vulnerability_archival/_index.md +++ b/doc/user/application_security/vulnerability_archival/_index.md @@ -61,7 +61,7 @@ Prerequisites: To download a vulnerability archive: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Security configuration**, then select **Vulnerability Management**. +1. Select **Secure** > **Security configuration**, then select **Vulnerability Management**. 1. To download details of all vulnerabilities archived: - For a specific year, in the row for that year, select **Download all**. - For a specific year and month, expand the year, then in the row for that month select **Download** ({{< icon name="download" >}}). diff --git a/doc/user/application_security/vulnerability_report/_index.md b/doc/user/application_security/vulnerability_report/_index.md index b5f4b720a5428f..1745e8c7941840 100644 --- a/doc/user/application_security/vulnerability_report/_index.md +++ b/doc/user/application_security/vulnerability_report/_index.md @@ -103,7 +103,7 @@ Prerequisites: To view the vulnerability report: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. ## Filtering vulnerabilities @@ -149,7 +149,7 @@ Filter the vulnerability report to focus on a subset of vulnerabilities. To filter the list of vulnerabilities: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Optional. To remove the default filters, select **Clear** ({{< icon name="clear" >}}). 1. Above the list of vulnerabilities, select the filter bar. 1. In the dropdown list that appears, select an attribute you want to filter by, then select the @@ -264,7 +264,7 @@ You can group by: To group vulnerabilities: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. From the **Group By** dropdown list, select a group. Vulnerabilities are grouped according to the group you selected. Each group is collapsed, with @@ -297,7 +297,7 @@ Prerequisites: To change the status of vulnerabilities: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. To select: - One or more vulnerabilities, select the checkbox beside each vulnerability. - All vulnerabilities on the page, select the checkbox in the table header. @@ -338,7 +338,7 @@ Prerequisites: To manually override a vulnerability's severity: 1. On the left sidebar, select **Search or go to** and find your project. -1. Go to **Secure > Vulnerability report**. +1. Go to **Secure** > **Vulnerability report**. 1. Select vulnerabilities: - To select individual vulnerabilities, select the checkbox beside each vulnerability. - To select all vulnerabilities on the page, select the checkbox in the table header. @@ -398,7 +398,7 @@ Prerequisites: To attach vulnerabilities to an existing issue: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Go to **Secure > Vulnerability report**. +1. Go to **Secure** > **Vulnerability report**. 1. Select vulnerabilities: - To select individual vulnerabilities, select the checkbox beside each vulnerability. - To select all vulnerabilities on the page, select the checkbox in the table header. @@ -429,7 +429,7 @@ Prerequisites: To attach vulnerabilities to a new issue: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Go to **Secure > Vulnerability report**. +1. Go to **Secure** > **Vulnerability report**. 1. Select vulnerabilities: - To select individual vulnerabilities, select the checkbox beside each vulnerability. - To select all vulnerabilities on the page, select the checkbox in the table header. @@ -527,7 +527,7 @@ can add a vulnerability only in a project's vulnerability report. To add a vulnerability manually: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Vulnerability report**. +1. Select **Secure** > **Vulnerability report**. 1. Select **Submit vulnerability**. 1. Complete the fields and submit the form. diff --git a/doc/user/clusters/agent/ci_cd_workflow.md b/doc/user/clusters/agent/ci_cd_workflow.md index 96655eeac5b692..96adf34d9787e0 100644 --- a/doc/user/clusters/agent/ci_cd_workflow.md +++ b/doc/user/clusters/agent/ci_cd_workflow.md @@ -156,7 +156,7 @@ To allow agents to be configured to authorize all projects in your GitLab instan {{< tab title="Using the UI" >}} -1. In the **Admin** area, select **Settings > General**, and expand the **GitLab agent for Kubernetes** section. +1. In the **Admin** area, select **Settings** > **General**, and expand the **GitLab agent for Kubernetes** section. 1. Select **Enable instance level authorization**. 1. Select **Save changes**. diff --git a/doc/user/clusters/agent/getting_started.md b/doc/user/clusters/agent/getting_started.md index d3fd1e47f5034d..d4c746c73c4351 100644 --- a/doc/user/clusters/agent/getting_started.md +++ b/doc/user/clusters/agent/getting_started.md @@ -136,7 +136,7 @@ The `glab cluster agent bootstrap` created an environment within GitLab and [con To view your dashboard: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Environments**. +1. Select **Operate** > **Environments**. 1. Select your environment. For example, `flux-system/gitlab-agent`. 1. Select the **Kubernetes overview** tab. diff --git a/doc/user/clusters/agent/getting_started_deployments.md b/doc/user/clusters/agent/getting_started_deployments.md index ba532798780738..d60edf7ac642d4 100644 --- a/doc/user/clusters/agent/getting_started_deployments.md +++ b/doc/user/clusters/agent/getting_started_deployments.md @@ -81,7 +81,7 @@ To learn more about enterprise best practices, see [enterprise considerations](e In this section, you'll build a simple Kubernetes manifest as an OCI artifact, then deploy it to your cluster. 1. Run the following `flux` CLI commands to tell Flux where to retrieve the specified OCI image and deploy its content. - Adjust the `--url` value for your GitLab instance. You can find the container registry URL under **Deploy > Container registry**. + Adjust the `--url` value for your GitLab instance. You can find the container registry URL under **Deploy** > **Container registry**. You can inspect the created `clusters/testing/nginx.yaml` file to better understand how Flux finds the manifests to deploy. ```shell @@ -185,7 +185,7 @@ In this section, you'll build a simple Kubernetes manifest as an OCI artifact, t ``` 1. Commit and push the changes to your project, and wait for the build pipeline to finish. -1. On the left sidebar, select **Operate > Environments** and check the available [dashboard for Kubernetes](../../../ci/environments/kubernetes_dashboard.md). +1. On the left sidebar, select **Operate** > **Environments** and check the available [dashboard for Kubernetes](../../../ci/environments/kubernetes_dashboard.md). The `applications/nginx` environment should be healthy. ## Secure the GitLab pipeline access diff --git a/doc/user/clusters/agent/install/_index.md b/doc/user/clusters/agent/install/_index.md index 8cbd42dc7a5154..d718f9f3eef4b5 100644 --- a/doc/user/clusters/agent/install/_index.md +++ b/doc/user/clusters/agent/install/_index.md @@ -121,7 +121,7 @@ You must register an agent before you can install the agent in your cluster. To 1. On the left sidebar, select **Search or go to** and find your project. If you have an [agent configuration file](#create-an-agent-configuration-file), it must be in this project. Your cluster manifest files should also be in this project. -1. Select **Operate > Kubernetes clusters**. +1. Select **Operate** > **Kubernetes clusters**. 1. Select **Connect a cluster (agent)**. 1. In the **Name of new agent** field, enter a unique name for your agent. - If an [agent configuration file](#create-an-agent-configuration-file) with this name already exists, it is used. diff --git a/doc/user/clusters/agent/user_access.md b/doc/user/clusters/agent/user_access.md index 3d65e203733869..e8bbfc52220500 100644 --- a/doc/user/clusters/agent/user_access.md +++ b/doc/user/clusters/agent/user_access.md @@ -227,7 +227,7 @@ glab cluster agent update-kubeconfig --agent '' --kubeconfig ~/gitlab. You can configure access to a Kubernetes cluster using a long-lived personal access token: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Kubernetes clusters** and retrieve the numerical ID of the agent you want to access. You need the ID to construct the full API token. +1. Select **Operate** > **Kubernetes clusters** and retrieve the numerical ID of the agent you want to access. You need the ID to construct the full API token. 1. Create a [personal access token](../../profile/personal_access_tokens.md) with the `k8s_proxy` scope. You need the access token to construct the full API token. 1. Construct `kubeconfig` entries to access the cluster: 1. Make sure that the proper `kubeconfig` is selected. diff --git a/doc/user/clusters/agent/vulnerabilities.md b/doc/user/clusters/agent/vulnerabilities.md index ac29e75a6bd813..4d943166c96ea1 100644 --- a/doc/user/clusters/agent/vulnerabilities.md +++ b/doc/user/clusters/agent/vulnerabilities.md @@ -302,7 +302,7 @@ To do this: To view vulnerability information in GitLab: 1. On the left sidebar, select **Search or go to** and find the project that contains the agent configuration file. -1. Select **Operate > Kubernetes clusters**. +1. Select **Operate** > **Kubernetes clusters**. 1. Select the **Agent** tab. 1. Select an agent to view the cluster vulnerabilities. diff --git a/doc/user/clusters/agent/work_with_agent.md b/doc/user/clusters/agent/work_with_agent.md index 0e047c38a179b8..69400d89e2396e 100644 --- a/doc/user/clusters/agent/work_with_agent.md +++ b/doc/user/clusters/agent/work_with_agent.md @@ -26,7 +26,7 @@ To view the list of agents: 1. On the left sidebar, select **Search or go to** and find the project that contains your agent configuration file. You cannot view registered agents from a project that does not contain the agent configuration file. -1. Select **Operate > Kubernetes clusters**. +1. Select **Operate** > **Kubernetes clusters**. 1. Select **Agent** tab to view clusters connected to GitLab through the agent. On this page, you can view: @@ -69,7 +69,7 @@ is shared with a project, it automatically appears in the project agent tab. To view the list of shared agents: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Kubernetes clusters**. +1. Select **Operate** > **Kubernetes clusters**. 1. Select the **Agent** tab. The list of shared agents and their clusters are displayed. @@ -81,7 +81,7 @@ you need for troubleshooting. You can see events from a week before the current date. To view an agent's activity: 1. On the left sidebar, select **Search or go to** and find the project that contains your agent configuration file. -1. Select **Operate > Kubernetes clusters**. +1. Select **Operate** > **Kubernetes clusters**. 1. Select the agent you want to see activity for. The activity list includes: @@ -148,7 +148,7 @@ To reset the agent token without downtime: 1. Create a new token: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Operate > Kubernetes clusters**. + 1. Select **Operate** > **Kubernetes clusters**. 1. Select the agent you want to create a token for. 1. On the **Access tokens** tab, select **Create token**. 1. Enter token's name and description (optional) and select **Create token**. @@ -168,7 +168,7 @@ clean up those resources manually. To remove an agent from the UI: 1. On the left sidebar, select **Search or go to** and find the project that contains the agent configuration file. -1. Select **Operate > Kubernetes clusters**. +1. Select **Operate** > **Kubernetes clusters**. 1. In the table, in the row for your agent, in the **Options** column, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}). 1. Select **Delete agent**. diff --git a/doc/user/clusters/management_project.md b/doc/user/clusters/management_project.md index 53c7cf50e9099e..ff1e661fcd9b92 100644 --- a/doc/user/clusters/management_project.md +++ b/doc/user/clusters/management_project.md @@ -72,7 +72,7 @@ To associate a cluster management project with your cluster: 1. Go to the appropriate configuration page. For a: - [Project-level cluster](../project/clusters/_index.md), go to your project's - **Operate > Kubernetes clusters** page. + **Operate** > **Kubernetes clusters** page. - [Group-level cluster](../group/clusters/_index.md), go to your group's **Kubernetes** page. - [Instance-level cluster](../instance/clusters/_index.md): diff --git a/doc/user/compliance/audit_event_streaming.md b/doc/user/compliance/audit_event_streaming.md index 7a52cb25a4e57b..a99fa180dc3202 100644 --- a/doc/user/compliance/audit_event_streaming.md +++ b/doc/user/compliance/audit_event_streaming.md @@ -66,7 +66,7 @@ Prerequisites: To add streaming destinations to a top-level group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select **Add streaming destination** and select **HTTP endpoint** to show the section for adding destinations. 1. In the **Name** and **Destination URL** fields, add a destination name and URL. @@ -85,7 +85,7 @@ Prerequisites: To update a streaming destination's name: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the stream to expand. 1. In the **Name** fields, add a destination name to update. @@ -94,7 +94,7 @@ To update a streaming destination's name: To update a streaming destination's custom HTTP headers: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the stream to expand. 1. Locate the **Custom HTTP headers** table. @@ -127,7 +127,7 @@ Prerequisites: To list streaming destinations and see the verification tokens: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the stream to expand. 1. Locate the **Verification token** input. @@ -148,7 +148,7 @@ A streaming destination that has an event type filter set has a **filtered** ({{ To update a streaming destination's event filters: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the stream to expand. 1. Locate the **Filter by audit event type** dropdown list. @@ -171,7 +171,7 @@ A streaming destination that has a namespace filter set has a **filtered** ({{< To update a streaming destination's namespace filters: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the stream to expand. 1. Locate the **Filter by groups or projects** dropdown list. @@ -217,7 +217,7 @@ Prerequisites: To add Google Cloud Logging streaming destinations to a top-level group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select **Add streaming destination** and select **Google Cloud Logging** to show the section for adding destinations. 1. Enter a random string to use as a name for the new destination. @@ -240,7 +240,7 @@ Prerequisites: To update Google Cloud Logging streaming destinations to a top-level group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the Google Cloud Logging stream to expand. 1. Enter a random string to use as a name for the destination. @@ -277,7 +277,7 @@ Prerequisites: To add AWS S3 streaming destinations to a top-level group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select **Add streaming destination** and select **AWS S3** to show the section for adding destinations. 1. Enter a random string to use as a name for the new destination. @@ -294,7 +294,7 @@ Prerequisites: To update an AWS S3 streaming destination to a top-level group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the AWS S3 stream to expand. 1. Enter a random string to use as a name for the destination. @@ -312,7 +312,7 @@ Prerequisites: To list streaming destinations for a top-level group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the stream to expand. @@ -340,7 +340,7 @@ Prerequisites: To deactivate a streaming destination: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the stream to expand. 1. Clear the **Active** checkbox. @@ -353,7 +353,7 @@ The destination stops receiving audit events. To reactivate a previously deactivated streaming destination: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the stream to expand. 1. Select the **Active** checkbox. @@ -373,7 +373,7 @@ Prerequisites: To delete streaming destinations to a top-level group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the stream to expand. 1. Select **Delete destination**. @@ -388,7 +388,7 @@ Prerequisites: To delete only the custom HTTP headers for a streaming destination: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. On the main area, select the **Streams** tab. 1. Select the stream to expand. 1. Locate the **Custom HTTP headers** table. diff --git a/doc/user/compliance/audit_events.md b/doc/user/compliance/audit_events.md index bc91ebaee0462e..d6f0448f51775d 100644 --- a/doc/user/compliance/audit_events.md +++ b/doc/user/compliance/audit_events.md @@ -52,7 +52,7 @@ Audit events can be viewed at the group, project, instance, and sign-in level. E Successful sign-in events are the only audit events available at all tiers. To see successful sign-in events: 1. On the left sidebar, select your avatar. -1. Select **Edit profile > Authentication log**. +1. Select **Edit profile** > **Authentication log**. After upgrading to a paid tier, you can also see successful sign-in events on audit event pages. @@ -68,7 +68,7 @@ After upgrading to a paid tier, you can also see successful sign-in events on au To view a group's audit events: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. Filter the audit events by the member of the project (user) who performed the action and date range. Group audit events can also be accessed using the [group audit events API](../../api/audit_events.md#group-audit-events). Group audit event queries `created_after` and `created_before` parameters are limited to a maximum 30 day difference between the dates. @@ -83,7 +83,7 @@ Group audit events can also be accessed using the [group audit events API](../.. {{< /details >}} 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Audit events**. +1. Select **Secure** > **Audit events**. 1. Filter the audit events by the member of the project (user) who performed the action and date range. Project audit events can also be accessed using the [project audit events API](../../api/audit_events.md#project-audit-events). Project audit event queries `created_after` and `created_before` parameters are limited to a maximum 30 day difference between the dates. diff --git a/doc/user/compliance/compliance_center/compliance_chain_of_custody_report.md b/doc/user/compliance/compliance_center/compliance_chain_of_custody_report.md index 92a957ec65d0b7..f89ebd320734f6 100644 --- a/doc/user/compliance/compliance_center/compliance_chain_of_custody_report.md +++ b/doc/user/compliance/compliance_center/compliance_chain_of_custody_report.md @@ -55,7 +55,7 @@ If the commit has a related merge commit, then the following are also included: To generate the Chain of Custody report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. In the top-right corner, select **Export**. 1. Select **Export chain of custody report**. @@ -76,7 +76,7 @@ details for the provided commit SHA. To generate a commit-specific Chain of Custody report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. In the top-right corner, select **Export**. 1. Select **Export custody report of a specific commit**. 1. Enter the commit SHA, and then select **Export custody report**. diff --git a/doc/user/compliance/compliance_center/compliance_frameworks_report.md b/doc/user/compliance/compliance_center/compliance_frameworks_report.md index 351af7e8472525..a01222060dbd5b 100644 --- a/doc/user/compliance/compliance_center/compliance_frameworks_report.md +++ b/doc/user/compliance/compliance_center/compliance_frameworks_report.md @@ -33,7 +33,7 @@ The default framework for the group has a **default** badge. To view the compliance frameworks report: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. ## Create a new compliance framework @@ -45,7 +45,7 @@ Prerequisites: To create a new compliance framework from the compliance frameworks report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Select the **New framework**. 1. Select **Create blank framework**. @@ -60,7 +60,7 @@ Prerequisites: To edit a compliance framework from the compliance frameworks report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Hover over framework and select **Edit the framework**. 1. Select the **Save changes** to edit compliance framework. @@ -74,7 +74,7 @@ Prerequisites: To delete a compliance framework from the compliance frameworks report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Hover over framework and select **Edit the framework**. 1. Select the **Delete framework** to delete compliance framework. @@ -94,7 +94,7 @@ Prerequisites: To set a compliance framework as [default](../compliance_frameworks/_index.md#default-compliance-frameworks)] from the compliance frameworks report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Next to the compliance framework you want to set as default, select {{< icon name="pencil" >}} action. 1. Select the **Set as default** to set as default. @@ -102,7 +102,7 @@ To set a compliance framework as [default](../compliance_frameworks/_index.md#de To remove a compliance framework as default from the compliance frameworks report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Next to the compliance framework that is default, select {{< icon name="pencil" >}} action. 1. Select the **Remove as default** to remove as default. @@ -125,7 +125,7 @@ Prerequisites: To export the standards adherence report for projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. In the top-right corner, select **Export**. 1. Select **Export framework report**. diff --git a/doc/user/compliance/compliance_center/compliance_projects_report.md b/doc/user/compliance/compliance_center/compliance_projects_report.md index ec987fb600fc8f..cc9657844cdea8 100644 --- a/doc/user/compliance/compliance_center/compliance_projects_report.md +++ b/doc/user/compliance/compliance_center/compliance_projects_report.md @@ -37,7 +37,7 @@ Prerequisites: To view the compliance projects report: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. ## Apply a compliance framework to projects in a group @@ -60,7 +60,7 @@ Prerequisites: To apply a compliance framework to one project in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. 1. Next to the project you want to add the compliance framework to, select {{< icon name="pencil" >}} action. 1. Select one or more existing compliance frameworks or create a new one. @@ -68,7 +68,7 @@ To apply a compliance framework to one project in a group: To apply a compliance framework to multiple projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. 1. Select multiple projects. 1. From the **Choose one bulk action** dropdown list, select **Apply framework to selected projects**. @@ -95,14 +95,14 @@ Prerequisites: To remove a compliance framework from one project in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. 1. Next to the compliance framework to remove from the project, select {{< icon name="close" >}} on the framework label. To remove a compliance framework from multiple projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. 1. Select multiple projects. 1. From the **Choose one bulk action** dropdown list, select **Remove framework from selected projects**. @@ -128,7 +128,7 @@ Prerequisites: To export a report of compliance frameworks on projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. In the top-right corner, select **Export**. 1. Select **Export list of project frameworks**. @@ -145,7 +145,7 @@ A report is compiled and delivered to your email inbox as an attachment. To filter the list of compliance frameworks: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. 1. In the search field: 1. Select the attribute you want to filter by. @@ -166,7 +166,7 @@ Prerequisites: To create a new compliance framework from the compliance projects report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. 1. Select the **+ Add framework**. 1. Select the **Create a new framework**. @@ -183,7 +183,7 @@ Prerequisites: To edit a compliance framework from the compliance projects report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. 1. Hover over framework and select **Edit the framework**. 1. Select the **Save changes** to edit compliance framework. @@ -199,7 +199,7 @@ Prerequisites: To delete a compliance framework from the compliance projects report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. 1. Hover over framework and select **Edit the framework**. 1. Select the **Delete framework** to delete compliance framework. diff --git a/doc/user/compliance/compliance_center/compliance_standards_adherence_dashboard.md b/doc/user/compliance/compliance_center/compliance_standards_adherence_dashboard.md index 87ca59b12d7fac..85a836f911b9b3 100644 --- a/doc/user/compliance/compliance_center/compliance_standards_adherence_dashboard.md +++ b/doc/user/compliance/compliance_center/compliance_standards_adherence_dashboard.md @@ -50,7 +50,7 @@ Prerequisites: To view the compliance standards adherence dashboard: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. You can filter the compliance standards adherence dashboard on: @@ -154,7 +154,7 @@ Prerequisites: To export the compliance standards adherence report for projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. In the top-right corner, select **Export**. 1. Select **Export standards adherence report**. diff --git a/doc/user/compliance/compliance_center/compliance_status_report.md b/doc/user/compliance/compliance_center/compliance_status_report.md index 9f42b049bcf83d..29784a72268b2f 100644 --- a/doc/user/compliance/compliance_center/compliance_status_report.md +++ b/doc/user/compliance/compliance_center/compliance_status_report.md @@ -42,7 +42,7 @@ Prerequisites: To view the compliance status report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. In the **Compliance reports** section, select **Compliance status report**. ## Report details @@ -75,7 +75,7 @@ Prerequisites: To export the compliance status report for projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. In the top-right corner, select **Export**. 1. Select **Export compliance status report**. diff --git a/doc/user/compliance/compliance_center/compliance_violations_report.md b/doc/user/compliance/compliance_center/compliance_violations_report.md index 88b8a83e5174f8..e7c2480e0e4b82 100644 --- a/doc/user/compliance/compliance_center/compliance_violations_report.md +++ b/doc/user/compliance/compliance_center/compliance_violations_report.md @@ -42,7 +42,7 @@ Prerequisites: To view the compliance violations report: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. The compliance violations report displays: @@ -132,7 +132,7 @@ Prerequisites: To view the static compliance violations report: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. You can sort the compliance report on: @@ -205,7 +205,7 @@ Prerequisites: To export a report of merge request compliance violations for projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. In the top-right corner, select **Export**. 1. Select **Export violations report**. diff --git a/doc/user/compliance/compliance_frameworks/_index.md b/doc/user/compliance/compliance_frameworks/_index.md index a3b081bdb092fc..9da962338991d5 100644 --- a/doc/user/compliance/compliance_frameworks/_index.md +++ b/doc/user/compliance/compliance_frameworks/_index.md @@ -77,7 +77,7 @@ has the correct permissions. The GitLab UI presents a read-only view to discoura To apply a compliance framework to a project through a compliance framework: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. 1. Hover over a compliance framework, select the **Edit Framework** tab. 1. Select **Projects** section. @@ -103,7 +103,7 @@ A compliance framework that is set to default has a **default** label. To set as default (or remove the default) from [compliance projects report](../compliance_center/compliance_projects_report.md): 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Projects** tab. 1. Hover over a compliance framework, select the **Edit Framework** tab. 1. Select **Set as default**. @@ -112,7 +112,7 @@ To set as default (or remove the default) from [compliance projects report](../c To set as default (or remove the default) from [compliance framework report](../compliance_center/compliance_frameworks_report.md): 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Hover over a compliance framework, select the **Edit Framework** tab. 1. Select **Set as default**. @@ -144,7 +144,7 @@ With this feature, you can share and back up compliance frameworks. To export a compliance framework from the compliance center: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Locate the compliance framework you wish to export. 1. Select the vertical ellipsis ({{< icon name="ellipsis_v" >}}). @@ -159,7 +159,7 @@ With this feature, you can use shared or backed up compliance frameworks. The JS To import a compliance framework by using a JSON template: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Select **New framework**. 1. Select **Import framework**. @@ -290,7 +290,7 @@ Status checks fail if an external control stays in the pending state for more th To add an external control when creating or editing a framework: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Select **New framework** or edit an existing one. 1. In the **Requirements** section, select **New requirement**. @@ -327,7 +327,7 @@ If something changes outside of GitLab, you can set the [status of an external c To add a requirement when creating or editing a framework: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Select **New framework** or edit an existing one. 1. In the **Requirements** section, select **New requirement**. @@ -341,10 +341,10 @@ To add a requirement when creating or editing a framework: To edit a requirement when creating or editing a framework: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. On the page, select the **Frameworks** tab. 1. Select **New framework** or edit an existing one. -1. In the **Requirements** section, select **Action** > **Edit**. +1. In the **Requirements** section, select **Action**** > ****Edit**. 1. In the dialog edit **Name** and **Description**. 1. Select **Add a GitLab control** to add more controls. 1. In the control dropdown list search and select a control. diff --git a/doc/user/compliance/compliance_pipelines.md b/doc/user/compliance/compliance_pipelines.md index f61c9fdfa7b4a6..f709aa59a40650 100644 --- a/doc/user/compliance/compliance_pipelines.md +++ b/doc/user/compliance/compliance_pipelines.md @@ -65,7 +65,7 @@ Existing compliance pipelines must be migrated. Customers should migrate from co To migrate an existing compliance framework to use the pipeline execution policy type: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure > Compliance center**. +1. Select **Secure** > **Compliance center**. 1. [Edit](compliance_frameworks/_index.md#create-edit-or-delete-a-compliance-framework) the existing compliance framework. 1. In the banner than appears, select **Migrate pipeline to a policy** to create a new policy in the security policies. 1. Edit the compliance framework again to remove the compliance pipeline. @@ -108,7 +108,7 @@ To ensure that the correct compliance pipeline is included in a project: To configure a compliance pipeline: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Secure** > **Compliance Center**. +1. Select **Secure**** > ****Compliance Center**. 1. Select **Frameworks** section. 1. Select **New framework** section, add information of compliance framework including path to the compliance framework configuration. Use the `path/file.y[a]ml@group-name/project-name` format. For example: diff --git a/doc/user/compliance/license_approval_policies.md b/doc/user/compliance/license_approval_policies.md index 62038928760c27..9ffbb1ffee9606 100644 --- a/doc/user/compliance/license_approval_policies.md +++ b/doc/user/compliance/license_approval_policies.md @@ -55,7 +55,7 @@ To create a license approval policy: 1. [Link a security policy project](../application_security/policies/security_policy_projects.md#link-to-a-security-policy-project) to your development group, subgroup, or project (the Owner role is required). 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Secure > Policies**. +1. Select **Secure** > **Policies**. 1. Create a new [Merge request approval Policy](../application_security/policies/merge_request_approval_policies.md). 1. In your policy rule, select **License scanning**. diff --git a/doc/user/crm/_index.md b/doc/user/crm/_index.md index 118e6c5352c9ab..20fe069f5712e3 100644 --- a/doc/user/crm/_index.md +++ b/doc/user/crm/_index.md @@ -64,7 +64,7 @@ CRM features must also be enabled for the subgroup. To enable customer relations management in a group or subgroup: 1. On the left sidebar, select **Search or go to** and find your group or subgroup. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Select **Customer relations is enabled**. 1. Select **Save changes**. @@ -85,9 +85,9 @@ unless they have a contact source configured. To configure the contact source for a group or subgroup: 1. On the left sidebar, select **Search or go to** and find your group or subgroup. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. -1. Select **Contact source > Search for a group**. +1. Select **Contact source** > **Search for a group**. 1. Select the group from which you wish to source contacts. 1. Select **Save changes**. @@ -102,7 +102,7 @@ Prerequisites: To view a group's contacts: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Customer relations**. +1. Select **Plan** > **Customer relations**. ![Contacts list](crm_contacts_v14_10.png) @@ -115,7 +115,7 @@ Prerequisites: To create a contact: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Customer relations**. +1. Select **Plan** > **Customer relations**. 1. Select **New contact**. 1. Complete all required fields. 1. Select **Create new contact**. @@ -132,7 +132,7 @@ Prerequisites: To edit an existing contact: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Customer relations**. +1. Select **Plan** > **Customer relations**. 1. Next to the contact you wish to edit, select **Edit** ({{< icon name="pencil" >}}). 1. Edit the required fields. 1. Select **Save changes**. @@ -150,7 +150,7 @@ Each contact can be in one of two states: To change the state of a contact: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Customer relations**. +1. Select **Plan** > **Customer relations**. 1. Next to the contact you wish to edit, select **Edit** ({{< icon name="pencil" >}}). 1. Select or clear the **Active** checkbox. 1. Select **Save changes**. @@ -166,7 +166,7 @@ Prerequisites: To view a group's organizations: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Customer relations**. +1. Select **Plan** > **Customer relations**. 1. In the upper right, select **Organizations**. ![Organizations list](crm_organizations_v14_10.png) @@ -180,7 +180,7 @@ Prerequisites: To create an organization: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Customer relations**. +1. Select **Plan** > **Customer relations**. 1. In the upper right, select **Organizations**. 1. Select **New organization**. 1. Complete all required fields. @@ -198,7 +198,7 @@ Prerequisites: To edit an existing organization: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Customer relations**. +1. Select **Plan** > **Customer relations**. 1. In the upper right, select **Organizations**. 1. Next to the organization you wish to edit, select **Edit** ({{< icon name="pencil" >}}). 1. Edit the required fields. @@ -221,7 +221,7 @@ Prerequisites: To view a contact's issues, select a contact from the issue sidebar, or: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Customer relations**. +1. Select **Plan** > **Customer relations**. 1. Next to the contact whose issues you wish to view, select **View issues** ({{< icon name="issues" >}}). ### View issues linked to an organization @@ -233,7 +233,7 @@ Prerequisites: To view an organization's issues: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Customer relations**. +1. Select **Plan** > **Customer relations**. 1. In the upper right, select **Organizations**. 1. Next to the organization whose issues you wish to view, select **View issues** ({{< icon name="issues" >}}). diff --git a/doc/user/custom_roles/_index.md b/doc/user/custom_roles/_index.md index a1bfd2a15d1d19..121925cad60748 100644 --- a/doc/user/custom_roles/_index.md +++ b/doc/user/custom_roles/_index.md @@ -71,7 +71,7 @@ To create a custom member role: 1. On the left sidebar: - For GitLab.com, select **Search or go to** and find your group. - For GitLab Self-Managed and GitLab Dedicated, at the bottom, select **Admin**. -1. Select **Settings > Roles and permissions**. +1. Select **Settings** > **Roles and permissions**. 1. Select **New role**. 1. GitLab Self-Managed and GitLab Dedicated instances only. Select **Member role**. 1. Enter a name and description for the custom role. @@ -94,7 +94,7 @@ Prerequisites: To create a custom admin role: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Roles and permissions**. +1. Select **Settings** > **Roles and permissions**. 1. Select **New role**. 1. Select **Admin role**. 1. Enter a name and description for the custom role. @@ -124,7 +124,7 @@ To edit a custom role: 1. On the left sidebar: - For GitLab.com, select **Search or go to** and find your group. - For GitLab Self-Managed and GitLab Dedicated, at the bottom, select **Admin**. -1. Select **Settings > Roles and permissions**. +1. Select **Settings** > **Roles and permissions**. 1. Next to a custom role, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}) > **Edit role**. 1. Modify the role. 1. Select **Save role**. @@ -150,7 +150,7 @@ To view details of a custom role: 1. On the left sidebar: - For GitLab.com, select **Search or go to** and find your group. - For GitLab Self-Managed and GitLab Dedicated, at the bottom, select **Admin**. -1. Select **Settings > Roles and permissions**. +1. Select **Settings** > **Roles and permissions**. 1. Next to a custom role, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}) > **View details**. ## Delete a custom role @@ -167,7 +167,7 @@ To delete a custom role: 1. On the left sidebar: - For GitLab.com, select **Search or go to** and find your group. - For GitLab Self-Managed and GitLab Dedicated, at the bottom, select **Admin**. -1. Select **Settings > Roles and permissions**. +1. Select **Settings** > **Roles and permissions**. 1. Next to a custom role, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}) > **Delete role**. 1. On the confirmation dialog, select **Delete role**. @@ -188,7 +188,7 @@ Prerequisites: To assign a custom member role to an existing user: 1. On the left sidebar, select **Search or go to** and find your group or project. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. 1. In the **Role** column, select the role for an existing member. The **Role details** drawer opens. 1. From the **Role** dropdown list, select a role to assign to the member. 1. Select **Update role** to assign the role. @@ -206,7 +206,7 @@ Prerequisites: To assign a custom admin role to an existing user: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Overview > Users**. +1. Select **Overview** > **Users**. 1. Select **Edit** for a user. 1. In the **Access** section, set the access level to either **Regular** or **Auditor**. 1. From the **Admin area** dropdown list, select a custom admin role. @@ -291,7 +291,7 @@ Prerequisites: To link a custom admin role with an LDAP CN: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Roles and permissions**. +1. Select **Settings** > **Roles and permissions**. 1. On the **LDAP Synchronization** tab, select an **LDAP Server**. 1. In the **Sync method** field, select `Group cn`. 1. In the **Group cn** field, begin typing the CN of the group. A dropdown list appears with matching CNs in the configured `group_base`. @@ -310,7 +310,7 @@ Prerequisites: To link a custom admin role with an LDAP filter: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Roles and permissions**. +1. Select **Settings** > **Roles and permissions**. 1. On the **LDAP Synchronization** tab, select an **LDAP Server**. 1. In the **Sync method** field, select `User filter`. 1. In **User filter** box, enter a filter. For details, see [Set up LDAP user filter](../../administration/auth/ldap/_index.md#set-up-ldap-user-filter). diff --git a/doc/user/discussions/_index.md b/doc/user/discussions/_index.md index aa20f92b18f24a..d03995ef4b8f3a 100644 --- a/doc/user/discussions/_index.md +++ b/doc/user/discussions/_index.md @@ -93,8 +93,8 @@ When you mention a group in a comment, every member of the group gets a to-do it added to their to-do list. 1. On the left sidebar, select **Search or go to** and find your project. -1. For merge requests, select **Code > Merge requests**, and find your merge request. -1. For issues, select **Plan > Issues**, and find your issue. +1. For merge requests, select **Code** > **Merge requests**, and find your merge request. +1. For issues, select **Plan** > **Issues**, and find your issue. 1. In a comment, type `@` followed by the user, group, or subgroup namespace. For example, `@alex`, `@alex-team`, or `@alex-team/marketing`. 1. Select **Comment**. @@ -113,7 +113,7 @@ When you add comments to a merge request diff, these comments persist, even when To add a commit diff comment: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Merge requests**, and find your merge request. +1. Select **Code** > **Merge requests**, and find your merge request. 1. Select the **Commits** tab, then select the commit message. 1. By the line you want to comment on, hover over the line number and select **Comment** ({{< icon name="comment" >}}). You can select multiple lines by dragging the **Comment** ({{< icon name="comment" >}}) icon. @@ -127,7 +127,7 @@ To add a commit diff comment: The comment displays on the merge request's **Overview** tab. -The comment is not displayed on your project's **Code > Commits** page. +The comment is not displayed on your project's **Code** > **Commits** page. {{< alert type="note" >}} @@ -184,8 +184,8 @@ Prerequisites: To lock an issue or merge request: 1. On the left sidebar, select **Search or go to** and find your project. -1. For merge requests, select **Code > Merge requests**, and find your merge request. -1. For issues, select **Plan > Issues**, and find your issue. +1. For merge requests, select **Code** > **Merge requests**, and find your merge request. +1. For issues, select **Plan** > **Issues**, and find your issue. 1. In the upper-right corner, select **Merge request actions** or **Issue actions** ({{< icon name="ellipsis_v" >}}), then select **Lock discussion**. diff --git a/doc/user/duo_agent_platform/software_development_flow.md b/doc/user/duo_agent_platform/software_development_flow.md index cef1896a910645..111525927e4c5c 100644 --- a/doc/user/duo_agent_platform/software_development_flow.md +++ b/doc/user/duo_agent_platform/software_development_flow.md @@ -72,7 +72,7 @@ Before you can use the software development flow in Visual Studio Code (VS Code) To use the software development flow in VS Code, ensure your repository is properly connected. -1. In VS Code, on the top menu, select **Terminal > New Terminal**. +1. In VS Code, on the top menu, select **Terminal** > **New Terminal**. 1. Clone your repository: `git clone `. 1. Change to the directory where your repository was cloned and check out your branch: `git checkout `. 1. Ensure your project is selected: @@ -89,7 +89,7 @@ To use the software development flow in VS Code, ensure your repository is prope 1. On the left sidebar, select **Source Control** ({{< icon name="branch" >}}). 1. On the **Source Control** label, right-click and select **Repositories**. - 1. Next to your repository, select the ellipsis ({{< icon name=ellipsis_h >}}), then **Remote > Add Remote**. + 1. Next to your repository, select the ellipsis ({{< icon name=ellipsis_h >}}), then **Remote** > **Add Remote**. 1. Select **Add remote from GitLab**. 1. Choose a remote. diff --git a/doc/user/duo_agent_platform/troubleshooting.md b/doc/user/duo_agent_platform/troubleshooting.md index 0198d66e2174f2..a827aa8894f8a2 100644 --- a/doc/user/duo_agent_platform/troubleshooting.md +++ b/doc/user/duo_agent_platform/troubleshooting.md @@ -35,7 +35,7 @@ You can troubleshoot some issues by viewing debugging logs. - On Windows and Linux: Ctrl + , 1. Search for the setting **GitLab: Debug** and enable it. 1. Open the language server logs: - 1. In VS Code, select **View** > **Output**. + 1. In VS Code, select **View**** > ****Output**. 1. In the output panel at the bottom, in the upper-right corner, select **GitLab Workflow** or **GitLab Language Server** from the list. 1. Review for errors, warnings, connection issues, or authentication problems. @@ -90,7 +90,7 @@ You might have a Git repository but it's not properly connected to GitLab. 1. On the left sidebar, select **Source Control** ({{< icon name="branch" >}}). 1. On the **Source Control** label, right-click and select **Repositories**. -1. Next to your repository, select the ellipsis ({{< icon name=ellipsis_h >}}), then **Remote > Add Remote**. +1. Next to your repository, select the ellipsis ({{< icon name=ellipsis_h >}}), then **Remote** > **Add Remote**. 1. Enter your GitLab project URL. 1. Select the newly added remote as your upstream. diff --git a/doc/user/free_user_limit.md b/doc/user/free_user_limit.md index 28f1298a07aa57..56fd6972f92698 100644 --- a/doc/user/free_user_limit.md +++ b/doc/user/free_user_limit.md @@ -85,7 +85,7 @@ Prerequisites: - You must have the Owner role for the group. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > Usage Quotas**. +1. Select **Settings** > **Usage Quotas**. 1. To view all members, select the **Seats** tab. On this page, you can view and manage all members in your namespace. For example, diff --git a/doc/user/gitlab_duo/context_exclusion.md b/doc/user/gitlab_duo/context_exclusion.md index 7c3d47952824fa..216a2cf8fd80f0 100644 --- a/doc/user/gitlab_duo/context_exclusion.md +++ b/doc/user/gitlab_duo/context_exclusion.md @@ -18,7 +18,7 @@ You can control which project content is included as context for GitLab Duo. Use ### Manage GitLab Duo context exclusions 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. Under **GitLab Duo**, in the **GitLab Duo Content Exclusions section**, select **Manage exclusions**. 1. Specify which project files and directories are excluded from GitLab Duo context, and select **Save exclusions**. diff --git a/doc/user/gitlab_duo/model_context_protocol/_index.md b/doc/user/gitlab_duo/model_context_protocol/_index.md index d70b5a4633e660..b92897fd6f05cb 100644 --- a/doc/user/gitlab_duo/model_context_protocol/_index.md +++ b/doc/user/gitlab_duo/model_context_protocol/_index.md @@ -52,7 +52,7 @@ Before you can use an AI-native feature with MCP, you must: To turn MCP on or off for your group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > GitLab Duo**. +1. Select **Settings** > **GitLab Duo**. 1. Select **Change configuration**. 1. Under **Model Context Protocol**, select or clear the **Turn on Model Context Protocol (MCP) support** checkbox. diff --git a/doc/user/gitlab_duo/model_selection.md b/doc/user/gitlab_duo/model_selection.md index 9597da57efb5b3..787dce4339daa1 100644 --- a/doc/user/gitlab_duo/model_selection.md +++ b/doc/user/gitlab_duo/model_selection.md @@ -46,7 +46,7 @@ Prerequisites: To select a different LLM for a feature: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > GitLab Duo**. +1. Select **Settings** > **GitLab Duo**. If you **GitLab Duo** is not visible, ensure you have GitLab Duo Core, Pro or Enterprise turned on for the group. 1. Select **Configure features**. diff --git a/doc/user/gitlab_duo/turn_on_off.md b/doc/user/gitlab_duo/turn_on_off.md index 170af40b37ed2d..cfbd2a2a4f2ee0 100644 --- a/doc/user/gitlab_duo/turn_on_off.md +++ b/doc/user/gitlab_duo/turn_on_off.md @@ -57,7 +57,7 @@ Prerequisites: To change GitLab Duo Core availability: 1. On the left sidebar, select **Search or go to** and find your top-level group. -1. Select **Settings > GitLab Duo**. +1. Select **Settings** > **GitLab Duo**. 1. Select **Change configuration**. 1. Under **GitLab Duo availability in this namespace**, select an option. 1. Under **GitLab Duo Core**, select or clear the **Turn on IDE features** checkbox. @@ -105,7 +105,7 @@ Prerequisites: To change GitLab Duo Core availability for the top-level group: 1. On the left sidebar, select **Search or go to** and find your top-level group. -1. Select **Settings > GitLab Duo**. +1. Select **Settings** > **GitLab Duo**. 1. Select **Change configuration**. 1. Under **GitLab Duo availability in this namespace**, select an option. 1. Select **Save changes**. @@ -121,7 +121,7 @@ Prerequisites: To change GitLab Duo Core availability for a group or subgroup: 1. On the left sidebar, select **Search or go to** and find your group or subgroup. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **GitLab Duo features**. 1. Under **GitLab Duo availability in this group**, select an option. 1. Select **Save changes**. @@ -137,7 +137,7 @@ Prerequisites: To change GitLab Duo Core availability for a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **GitLab Duo**. 1. Turn the **Use AI-native features in this project** toggle on or off. 1. Select **Save changes**. @@ -172,7 +172,7 @@ Prerequisites: To turn GitLab Duo on or off for a group or subgroup: 1. On the left sidebar, select **Search or go to** and find your group or subgroup. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **GitLab Duo features**. 1. Under **GitLab Duo availability in this group**, select an option. 1. Select **Save changes**. @@ -188,7 +188,7 @@ Prerequisites: To turn GitLab Duo on or off for a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **GitLab Duo**. 1. Turn the **Use AI-native features in this project** toggle on or off. 1. Select **Save changes**. @@ -235,7 +235,7 @@ Prerequisites: To turn on GitLab Duo experiment and beta features for a top-level group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > GitLab Duo**. +1. Select **Settings** > **GitLab Duo**. 1. Under **GitLab Duo** section, select **Change configuration**. 1. Under **Feature preview**, select **Turn on experiment and beta GitLab Duo features**. 1. Select **Save changes**. @@ -248,7 +248,7 @@ In GitLab 17.3 and earlier, follow these instructions to turn on GitLab Duo experimental and beta features for your group on GitLab.com. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. Under **GitLab Duo experiment and beta features**, select the **Use experiment and beta GitLab Duo features** checkbox. 1. Select **Save changes**. @@ -283,7 +283,7 @@ Prerequisites: To turn on GitLab Duo experiment and beta features for an instance: 1. On the left sidebar, at the bottom, select **Admin area**. -1. Select **Settings > GitLab Duo**. +1. Select **Settings** > **GitLab Duo**. 1. Expand **Change configuration**. 1. Under **Feature Preview**, select **Use experiment and beta GitLab Duo features**. 1. Select **Save changes**. diff --git a/doc/user/gitlab_duo/turn_on_off_earlier.md b/doc/user/gitlab_duo/turn_on_off_earlier.md index cb839692f4caa0..3c8acca8a601fa 100644 --- a/doc/user/gitlab_duo/turn_on_off_earlier.md +++ b/doc/user/gitlab_duo/turn_on_off_earlier.md @@ -45,9 +45,9 @@ To turn GitLab Duo on or off for a group or subgroup: 1. On the left sidebar, select **Search or go to** and find your group or subgroup. 1. Go to the settings, based on your deployment type and group level: - - For GitLab.com top-level groups: Select **Settings > GitLab Duo** and select **Change configuration**. - - For GitLab.com subgroups: Select **Settings > General** and expand **GitLab Duo features**. - - For GitLab Self-Managed (all groups and subgroups): Select **Settings > General** and expand **GitLab Duo features**. + - For GitLab.com top-level groups: Select **Settings** > **GitLab Duo** and select **Change configuration**. + - For GitLab.com subgroups: Select **Settings** > **General** and expand **GitLab Duo features**. + - For GitLab Self-Managed (all groups and subgroups): Select **Settings** > **General** and expand **GitLab Duo features**. 1. Choose an option. 1. Select **Save changes**. @@ -75,7 +75,7 @@ Prerequisites: To turn GitLab Duo on or off for a top-level group: 1. On the left sidebar, select **Search or go to** and find your top-level group. -1. Select **Settings > GitLab Duo**. +1. Select **Settings** > **GitLab Duo**. 1. Select **Change configuration**. 1. Choose an option. 1. Select **Save changes**. @@ -104,7 +104,7 @@ Prerequisites: To turn GitLab Duo on or off for a top-level group: 1. On the left sidebar, select **Search or go to** and find your top-level group. -1. Select **Settings > GitLab Duo**. +1. Select **Settings** > **GitLab Duo**. 1. Select **Change configuration**. 1. Choose an option. 1. Select **Save changes**. @@ -123,7 +123,7 @@ Prerequisites: To turn GitLab Duo on or off for a group or subgroup: 1. On the left sidebar, select **Search or go to** and find your group or subgroup. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. Select or clear the **Use GitLab Duo features** checkbox. 1. Optional. Select the **Enforce for all subgroups** checkbox to cascade the setting to @@ -150,7 +150,7 @@ Prerequisites: To turn GitLab Duo on or off for a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. Under **GitLab Duo**, turn the toggle on or off. 1. Select **Save changes**. @@ -211,7 +211,7 @@ Prerequisites: To turn GitLab Duo on or off for an instance: 1. On the left sidebar, at the bottom, select **Admin area**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **GitLab Duo features**. 1. Choose an option. 1. Select **Save changes**. @@ -229,7 +229,7 @@ Prerequisites: To turn GitLab Duo on or off for an instance: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **AI-powered features**. 1. Select or clear the **Use Duo features** checkbox. 1. Optional. Select the **Enforce for all subgroups** checkbox to cascade diff --git a/doc/user/gitlab_duo/tutorials/fix_code_python_shop.md b/doc/user/gitlab_duo/tutorials/fix_code_python_shop.md index 2c5503018a918c..8bc9681f157a51 100644 --- a/doc/user/gitlab_duo/tutorials/fix_code_python_shop.md +++ b/doc/user/gitlab_duo/tutorials/fix_code_python_shop.md @@ -71,7 +71,7 @@ Depending on your subscription add-on, you can use Chat in the GitLab UI, the We 1. Open the Web IDE: 1. In the GitLab UI, on the left sidebar, select **Search or go to** and find your project. - 1. Select a file. Then in the upper right, select **Edit > Open in Web IDE**. + 1. Select a file. Then in the upper right, select **Edit** > **Open in Web IDE**. 1. Open Chat by using one of these methods: - On the left sidebar, select **GitLab Duo Chat**. - In the file that you have open in the editor, select some code. diff --git a/doc/user/gitlab_duo_chat/_index.md b/doc/user/gitlab_duo_chat/_index.md index 35ca868cfc24a8..710f11fdcd1376 100644 --- a/doc/user/gitlab_duo_chat/_index.md +++ b/doc/user/gitlab_duo_chat/_index.md @@ -183,7 +183,7 @@ To use GitLab Duo Chat in the Web IDE on GitLab: 1. Open the Web IDE: 1. In the GitLab UI, on the left sidebar, select **Search or go to** and find your project. - 1. Select a file. Then in the upper right, select **Edit > Open in Web IDE**. + 1. Select a file. Then in the upper right, select **Edit** > **Open in Web IDE**. 1. Then open Chat by using one of the following methods: - On the left sidebar, select **GitLab Duo Chat**. - In the file that you have open in the editor, select some code. @@ -247,7 +247,7 @@ To open GitLab Duo Chat in the editor window, use any of these methods: - From a keyboard shortcut, by pressing: - MacOS: Option + c - Windows and Linux: ALT + c -- Right-clicking in the currently open file in your IDE, then selecting **GitLab Duo Chat > Open Quick Chat**. +- Right-clicking in the currently open file in your IDE, then selecting **GitLab Duo Chat** > **Open Quick Chat**. Optionally, select some code to provide additional context. - Opening the [Command Palette](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette), then selecting **GitLab Duo Chat: Open Quick Chat**. @@ -314,7 +314,7 @@ To open GitLab Duo Chat in a chat window, use any of these methods: - From a highlighted code issue: 1. Right-click and select **Show Context Actions**. 1. Select **Fix with Duo**. -- With a keyboard or mouse shortcut for a GitLab Duo action, which you can set in **Settings > Keymap**. +- With a keyboard or mouse shortcut for a GitLab Duo action, which you can set in **Settings** > **Keymap**. After GitLab Duo Chat opens: @@ -339,7 +339,7 @@ To open GitLab Duo Chat Quick Chat in the editor window, use any of these method - Windows and Linux: ALT + c - In an open file in your IDE, by selecting some code, then, in the floating toolbar, selecting **GitLab Duo Quick Chat** ({{< icon name="tanuki-ai" >}}). -- Right-clicking, then selecting **GitLab Duo Chat > Open Quick Chat**. +- Right-clicking, then selecting **GitLab Duo Chat** > **Open Quick Chat**. After Quick Chat opens: diff --git a/doc/user/gitlab_duo_chat/agentic_chat.md b/doc/user/gitlab_duo_chat/agentic_chat.md index 8481de108edb95..f5d97ab2485b43 100644 --- a/doc/user/gitlab_duo_chat/agentic_chat.md +++ b/doc/user/gitlab_duo_chat/agentic_chat.md @@ -87,7 +87,7 @@ You can only use Agentic Chat in a project: To use Agentic Chat: -1. In VS Code, go to **Settings > Settings**. +1. In VS Code, go to **Settings** > **Settings**. 1. Search for `gitlab agentic`. 1. Under **Gitlab › Duo Agentic Chat: Enabled**, select the **Enable GitLab Duo Agentic Chat** checkbox. diff --git a/doc/user/gitlab_duo_chat/examples.md b/doc/user/gitlab_duo_chat/examples.md index b2dae547bc63d6..b64f1552a9dcee 100644 --- a/doc/user/gitlab_duo_chat/examples.md +++ b/doc/user/gitlab_duo_chat/examples.md @@ -664,7 +664,7 @@ To troubleshoot a failed CI/CD job from a merge request: To troubleshoot a failed CI/CD job from the job log: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Build > Jobs**. +1. Select **Build** > **Jobs**. 1. Select the failed CI/CD job. 1. Below the job log, either: - Select **Troubleshoot**. diff --git a/doc/user/gitlab_duo_chat/turn_on_off.md b/doc/user/gitlab_duo_chat/turn_on_off.md index ca58f3fc889a5b..72b59a674e9149 100644 --- a/doc/user/gitlab_duo_chat/turn_on_off.md +++ b/doc/user/gitlab_duo_chat/turn_on_off.md @@ -49,7 +49,7 @@ In GitLab 16.11 and later, GitLab Duo Chat is: In GitLab 16.8, 16.9, and 16.10, GitLab Duo Chat is available in beta. To enable GitLab Duo Chat for GitLab Self-Managed, an administrator must enable experiment and beta features: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **AI-native features** and select **Enable Experiment and Beta AI-native features**. 1. Select **Save changes**. 1. To make sure GitLab Duo Chat works immediately, you must diff --git a/doc/user/group/_index.md b/doc/user/group/_index.md index 7f9111ca41380e..4abccf3dc42575 100644 --- a/doc/user/group/_index.md +++ b/doc/user/group/_index.md @@ -169,7 +169,7 @@ To find the Group ID: To view the activity of a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Activity**. +1. Select **Manage** > **Activity**. 1. Optional. To filter activity by contribution type, select a tab: - **All**: All contributions by group members in the group and group's projects. @@ -215,7 +215,7 @@ Prerequisites: To edit group details: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. In the **Group name** text box, enter your group name. See the [limitations on group names](../reserved_names.md). 1. Optional. In the **Group description (optional)** text box, enter your group description. The description is limited to 500 characters. @@ -253,7 +253,7 @@ To leave a group: To delete a group and its contents: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Advanced** section. 1. In the **Delete group** section, select **Delete group**. 1. On the confirmation dialog, type the group name and select **Confirm**. @@ -314,7 +314,7 @@ Prerequisites: To immediately delete a group marked for deletion: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Advanced**. 1. In the **Permanently delete group** section, select **Delete group**. 1. Confirm the action when asked to. @@ -326,7 +326,7 @@ This action deletes the group, its subgroups, projects, and all related resource To restore a group that is marked for deletion: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Advanced** section. 1. In the **Restore group** section, select **Restore group**. @@ -352,7 +352,7 @@ If you change your mind before your request is approved, select To view members of a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. A table displays the member's: @@ -390,7 +390,7 @@ In lists of group members, entries can display the following badges: - **Enterprise**, to indicate that the member of the top-level group is an [enterprise user](../enterprise_user/_index.md). 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. 1. Above the list of members, in the **Filter members** text box, enter your search criteria. To view: - Direct members of the group, select **Membership = Direct**. - Inherited, shared, and inherited shared members of the group, select **Membership = Indirect**. @@ -402,7 +402,7 @@ In lists of group members, entries can display the following badges: You can search for members by name, username, or [public email](../profile/_index.md#set-your-public-email). 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. 1. Above the list of members, in the **Filter members** box, enter search criteria. 1. To the right of the **Filter members** box, select the magnifying glass ({{< icon name="search" >}}). @@ -411,7 +411,7 @@ You can search for members by name, username, or [public email](../profile/_inde You can sort members by **Account**, **Access granted**, **Role**, or **Last sign-in**. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. 1. Above the list of members, in the upper-right corner, from the **Account** list, select the criteria to filter by. 1. To switch the sort between ascending and descending, to the right of the **Account** list, select the @@ -437,7 +437,7 @@ Prerequisites: - If [administrator approval is enabled](../../administration/settings/sign_up_restrictions.md#turn-on-administrator-approval-for-role-promotions), an administrator must approve the invitation. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. 1. Select **Invite members**. 1. If the user: @@ -480,7 +480,7 @@ If [administrator approval for role promotions](../../administration/settings/si To view users pending promotion: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. 1. Select the **Role promotions** tab. If the **Role promotions** tab is not displayed, the group has no pending promotions. @@ -497,7 +497,7 @@ Prerequisites: To remove a member from a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. 1. Next to the member you want to remove, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}). 1. Select **Remove member**. 1. Optional. On the **Remove member** confirmation dialog, select one or both checkboxes: @@ -527,7 +527,7 @@ By default, users with at least the: To specify which roles can create projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. From **Minimum role required to create projects**, select an option. 1. Select **Save changes**. diff --git a/doc/user/group/access_and_permissions.md b/doc/user/group/access_and_permissions.md index 31df0976479200..f6233f5d94f2a7 100644 --- a/doc/user/group/access_and_permissions.md +++ b/doc/user/group/access_and_permissions.md @@ -35,7 +35,7 @@ Group push rules allow group maintainers to set To configure push rules for a group: -1. On the left sidebar, select **Settings > Repository**. +1. On the left sidebar, select **Settings** > **Repository**. 1. Expand the **Pre-defined push rules** section. 1. Select the settings you want. 1. Select **Save push rules**. @@ -61,7 +61,7 @@ configured by an administrator. To change the permitted Git access protocols for a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Choose the permitted protocols from **Enabled Git access protocols**. 1. Select **Save changes**. @@ -114,7 +114,7 @@ proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; To restrict group access by IP address: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. In the **Restrict access by IP address** text box, enter a list of IPv4 or IPv6 address ranges in CIDR notation. This list: @@ -174,7 +174,7 @@ to access that group. Subgroups inherit the same allowlist. To restrict group access by domain: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. In the **Restrict membership by email** field, enter the domain names to allow. 1. Select **Save changes**. @@ -206,7 +206,7 @@ As a group Owner, you can prevent non-members from requesting access to your group. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Clear the **Allow users to request access** checkbox. 1. Select **Save changes**. @@ -239,7 +239,7 @@ Prerequisites: To prevent projects from being forked outside the group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Check **Prevent project forking outside current group**. 1. Select **Save changes**. @@ -271,7 +271,7 @@ The setting does not cascade. Projects in subgroups observe the subgroup configu To prevent members from being added to projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Under **Membership**, select **Users cannot be added to projects in this group**. 1. Select **Save changes**. @@ -298,7 +298,7 @@ After you lock the membership for a group: Group syncing allows LDAP groups to be mapped to GitLab groups. This provides more control over per-group user management. To configure group syncing, edit the `group_base` **DN** (`'OU=Global Groups,OU=GitLab INT,DC=GitLab,DC=org'`). This **OU** contains all groups that are associated with GitLab groups. -Group links can be created by using either a CN or a filter. To create these group links, go to the group's **Settings > LDAP Synchronization** page. After configuring the link, it may take more than an hour for the users to sync with the GitLab group. After you have configured the link: +Group links can be created by using either a CN or a filter. To create these group links, go to the group's **Settings** > **LDAP Synchronization** page. After configuring the link, it may take more than an hour for the users to sync with the GitLab group. After you have configured the link: - In GitLab 16.7 and earlier, group Owners cannot add members to or remove members from the group. The LDAP server is considered the single source of truth for group membership for all users who have signed in with LDAP credentials. - In GitLab 16.8 and later, group Owners can use the [member roles API](../../api/member_roles.md) or [group members API](../../api/members.md#add-a-member-to-a-group-or-project) to add a service account user to or remove a service account user from the group, even when LDAP synchronization is enabled for the group. Group Owners cannot add or remove non-service account users. @@ -371,7 +371,7 @@ To create group links with an LDAP user filter: LDAP user permissions can be manually overridden by an administrator. To override a user's permissions: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Members**. If LDAP synchronization +1. Select **Manage** > **Members**. If LDAP synchronization has granted a user a role with: - More permissions than the parent group membership, that user is displayed as having [direct membership](../project/members/_index.md#display-direct-members) of the group. diff --git a/doc/user/group/clusters/_index.md b/doc/user/group/clusters/_index.md index ff2ad948ba57b2..6137735ad48031 100644 --- a/doc/user/group/clusters/_index.md +++ b/doc/user/group/clusters/_index.md @@ -27,7 +27,7 @@ your group, enabling you to use the same cluster across multiple projects. To view your group-level Kubernetes clusters: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Operate > Kubernetes**. +1. Select **Operate** > **Kubernetes**. ## Cluster management project @@ -85,7 +85,7 @@ your cluster, which can cause deployment jobs to fail. To clear the cache: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Operate > Kubernetes**. +1. Select **Operate** > **Kubernetes**. 1. Select your cluster. 1. Expand **Advanced settings**. 1. Select **Clear cluster cache**. diff --git a/doc/user/group/contribution_analytics/_index.md b/doc/user/group/contribution_analytics/_index.md index d096c0fbaa85a2..53a711a12b0195 100644 --- a/doc/user/group/contribution_analytics/_index.md +++ b/doc/user/group/contribution_analytics/_index.md @@ -42,7 +42,7 @@ GitLab records five commits, though the user made three unique commits. To view contribution analytics: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Analyze > Contribution analytics**. +1. Select **Analyze** > **Contribution analytics**. 1. Optional. Filter the results: - To view contribution analytics for last week, month, or three months, select one of the three tabs. diff --git a/doc/user/group/custom_project_templates.md b/doc/user/group/custom_project_templates.md index 9a439ce0839ed0..2129b1041fd445 100644 --- a/doc/user/group/custom_project_templates.md +++ b/doc/user/group/custom_project_templates.md @@ -35,7 +35,7 @@ project templates to the group settings: 1. In the group, create a [subgroup](subgroups/_index.md). 1. [Add projects to the new subgroup](_index.md#add-projects-to-a-group) as your templates. -1. In the left menu for the group, select **Settings > General**. +1. In the left menu for the group, select **Settings** > **General**. 1. Expand **Custom project templates** and select the subgroup. The next time a group member creates a project, they can select any of the projects in the subgroup. diff --git a/doc/user/group/devops_adoption/_index.md b/doc/user/group/devops_adoption/_index.md index 17983d28cf833f..668d7659dc9010 100644 --- a/doc/user/group/devops_adoption/_index.md +++ b/doc/user/group/devops_adoption/_index.md @@ -78,7 +78,7 @@ Prerequisites: To view DevOps adoption: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Analyze > DevOps adoption**. +1. Select **Analyze** > **DevOps adoption**. 1. To view the features adopted by category in a month, hover over a bar. ## Add a subgroup to DevOps adoption @@ -90,7 +90,7 @@ Prerequisites: To add a subgroup to the DevOps adoption report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Analyze > DevOps adoption**. +1. Select **Analyze** > **DevOps adoption**. 1. From the **Add or remove subgroups** dropdown list, select the subgroup you want to add. ## Remove a subgroup from DevOps adoption @@ -102,7 +102,7 @@ Prerequisites: To remove a subgroup from the DevOps adoption report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Analyze > DevOps adoption**. +1. Select **Analyze** > **DevOps adoption**. 1. Either: - From the **Add or remove subgroups** dropdown list, clear the subgroup you want to remove. diff --git a/doc/user/group/epics/epic_boards.md b/doc/user/group/epics/epic_boards.md index 8e50c75318e5f0..693c6be431f4df 100644 --- a/doc/user/group/epics/epic_boards.md +++ b/doc/user/group/epics/epic_boards.md @@ -35,7 +35,7 @@ On the top of each list, you can see the number of epics in the list ({{< icon n To view an epic board: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Epic boards**. +1. Select **Plan** > **Epic boards**. ![GitLab epic board - Premium](img/epic_board_v15_10.png) @@ -48,7 +48,7 @@ Prerequisites: To create a new epic board: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Epic boards**. +1. Select **Plan** > **Epic boards**. 1. In the upper-left corner, select the dropdown list with the current board name. 1. Select **Create new board**. 1. Enter the new board's title. @@ -101,7 +101,7 @@ Prerequisites: To create a new list: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Epic boards**. +1. Select **Plan** > **Epic boards**. 1. In the upper-right corner, select **New list**. 1. Hover or move keyboard focus between two lists. 1. Select **New list**. diff --git a/doc/user/group/epics/manage_epics.md b/doc/user/group/epics/manage_epics.md index 3c3b00e8df51a3..c7b2b33db61e95 100644 --- a/doc/user/group/epics/manage_epics.md +++ b/doc/user/group/epics/manage_epics.md @@ -145,7 +145,7 @@ Prerequisites: To update multiple epics at the same time: -1. In a group, go to **Epics > List**. +1. In a group, go to **Epics** > **List**. 1. Select **Bulk edit**. A sidebar on the right appears with editable fields. 1. Select the checkboxes next to each epic you want to edit. 1. Select the appropriate fields and their values from the sidebar. @@ -230,7 +230,7 @@ Prerequisites: To change the assignee on an epic: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Epics**, then select your epic to view it. +1. Select **Plan** > **Epics**, then select your epic to view it. 1. On the right sidebar, in the **Assignees** section, select **Edit**. 1. From the dropdown list, select the users to add as an assignee. 1. Select any area outside the dropdown list. @@ -285,7 +285,7 @@ Prerequisites: To change an epic's color: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Epics**. +1. Select **Plan** > **Epics**. 1. Select **New epic** or select an existing epic. 1. On the right sidebar, in the **Color** section, select **Edit**. 1. Select an existing color or enter an RGB or hex value. @@ -376,7 +376,7 @@ Prerequisites: To view epics in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Epics**. +1. Select **Plan** > **Epics**. ### Who can view an epic @@ -416,7 +416,7 @@ GitLab saves your display preferences at different levels: To configure epic display preferences: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan** > **Epics**. +1. Select **Plan**** > ****Epics**. 1. In the top right corner, select **Display options** ({{< icon name="preferences" >}}). 1. Under **Fields**, turn on or turn off the metadata you want to display: - **Assignee**: Who the epic is assigned to. @@ -472,7 +472,7 @@ To open an epic in the full page view: To configure how epics open on the Epics page: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Epics**. +1. Select **Plan** > **Epics**. 1. In the top right corner, select **Display options** ({{< icon name="preferences" >}}). 1. Toggle **Open items in side panel**: - **On** (default): Epics open in a drawer overlay. @@ -510,7 +510,7 @@ You can filter the list of epics by: To filter: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Epics**. +1. Select **Plan** > **Epics**. 1. Select the field **Search or filter results**. 1. From the dropdown list, select the scope or enter plain text to search by epic title or description. 1. Press Enter on your keyboard. The list is filtered. @@ -680,7 +680,7 @@ Prerequisites: To change the health status of an epic: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Epics**. +1. Select **Plan** > **Epics**. 1. Select an epic. 1. In the right sidebar, in the **Health status** section, select **Edit**. 1. From the dropdown list, select a status. @@ -869,7 +869,7 @@ Prerequisites: To add a parent epic: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Epics**. +1. Select **Plan** > **Epics**. 1. Select an epic. 1. In the right sidebar, in the **Parent** section, select **Edit**. 1. In the search box, enter part of the parent epic's title. @@ -926,7 +926,7 @@ Prerequisites: To add a new epic as child epic: -1. In an epic, in the **Child items** section, select **Add > Add a new epic**. +1. In an epic, in the **Child items** section, select **Add** > **Add a new epic**. 1. Select a group from the dropdown list. The epic's group is selected by default. 1. Enter a title for the new epic. 1. Select **Create epic**. @@ -935,7 +935,7 @@ To add a new epic as child epic: To add an existing epic as child epic: -1. In an epic, in the **Child items** section, select **Add > Add an existing epic**. +1. In an epic, in the **Child items** section, select **Add** > **Add an existing epic**. 1. Identify the epic to be added, using either of the following methods: - Paste the link of the epic. - Search for the desired issue by entering part of the epic's title, then selecting the desired match. This search is only available for epics in the same group hierarchy. diff --git a/doc/user/group/import/troubleshooting.md b/doc/user/group/import/troubleshooting.md index 9be2dc168b3ae3..d285f6a2827e4a 100644 --- a/doc/user/group/import/troubleshooting.md +++ b/doc/user/group/import/troubleshooting.md @@ -116,7 +116,7 @@ To solve this, you must change the source group path to include a non-numerical - The GitLab UI: 1. On the left sidebar, select **Search or go to** and find your group. - 1. Select **Settings > General**. + 1. Select **Settings** > **General**. 1. Expand **Advanced**. 1. Under **Change group URL**, change the group URL to include non-numeric characters. diff --git a/doc/user/group/issues_analytics/_index.md b/doc/user/group/issues_analytics/_index.md index c6d2cdde37f8f1..867e4ab62ece5b 100644 --- a/doc/user/group/issues_analytics/_index.md +++ b/doc/user/group/issues_analytics/_index.md @@ -33,7 +33,7 @@ A table displays the top 100 issues based on the global page filters, with the f To view issue analytics: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Issue analytics**. To view the total number of issues for a month, hover over a bar. +1. Select **Analyze** > **Issue analytics**. To view the total number of issues for a month, hover over a bar. 1. Optional. To filter the results, in **Search or filter results** text box, enter your criteria: - Author diff --git a/doc/user/group/iterations/_index.md b/doc/user/group/iterations/_index.md index 2e6d0646b438b1..d8f20acbfb86d6 100644 --- a/doc/user/group/iterations/_index.md +++ b/doc/user/group/iterations/_index.md @@ -123,7 +123,7 @@ Prerequisites: To create an iteration cadence: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Iterations**. +1. Select **Plan** > **Iterations**. 1. Select **New iteration cadence**. 1. Enter the title and description of the iteration cadence. @@ -146,7 +146,7 @@ To manually manage the created cadence, see [Create an iteration manually](#crea ### View the iterations list 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Iterations**. +1. Select **Plan** > **Iterations**. To view all the iterations in a cadence, ordered by descending date, select that iteration cadence. From there you can create a new iteration or select an iteration to get a more detailed view. @@ -170,7 +170,7 @@ Prerequisites: To edit an iteration cadence: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Iterations**. +1. Select **Plan** > **Iterations**. 1. To the right of the cadence you want to edit, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}) and then select **Edit cadence**. 1. Edit the fields. @@ -185,7 +185,7 @@ To edit an iteration cadence: #### Turn on and off automatic scheduling for an iteration cadence 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Iterations**. +1. Select **Plan** > **Iterations**. 1. To the right of the cadence for which you want to turn on or off automatic scheduling, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}) and then select **Edit cadence**. 1. Select or clear the **Enable automatic scheduling** checkbox. @@ -240,7 +240,7 @@ Deleting an iteration cadence also deletes all iterations in that cadence. To delete an iteration cadence: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Iterations**. +1. Select **Plan** > **Iterations**. 1. To the right of the cadence you want to delete, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}) and then select **Delete cadence**. 1. Select **Delete cadence**. @@ -277,7 +277,7 @@ Prerequisites: To create an iteration: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Iterations**. +1. Select **Plan** > **Iterations**. 1. To the right of the cadence in which you want create an iteration, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}) and then select **Add iteration**. 1. Complete the fields. @@ -299,7 +299,7 @@ Prerequisites: To edit an iteration: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Iterations** and select an iteration cadence. +1. Select **Plan** > **Iterations** and select an iteration cadence. 1. Select the iteration you want edit. The iteration details page opens. 1. In the upper-right corner, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}) and then select **Edit**. 1. Edit the fields: @@ -323,7 +323,7 @@ Prerequisites: To delete an iteration: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Iterations** and select an iteration cadence. +1. Select **Plan** > **Iterations** and select an iteration cadence. 1. Select the iteration you want edit. The iteration details page opens. 1. In the upper-right corner, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}) and then select **Delete**. 1. Select **Delete**. @@ -342,7 +342,7 @@ Closed iteration reports show the total number of issues completed by the due da To view an iteration report: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Iterations** and select an iteration cadence. +1. Select **Plan** > **Iterations** and select an iteration cadence. 1. Select an iteration. ### Iteration burndown and burnup charts @@ -386,7 +386,7 @@ understanding of scope attributable to each label. To group issues by label: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Iterations** and select an iteration cadence. +1. Select **Plan** > **Iterations** and select an iteration cadence. 1. Select an iteration. 1. From the **Group by** dropdown list, select **Label**. 1. From the **Filter by label** dropdown list, select the labels you want to group by. diff --git a/doc/user/group/manage.md b/doc/user/group/manage.md index 5acde958b4ce8e..a8234d897773e9 100644 --- a/doc/user/group/manage.md +++ b/doc/user/group/manage.md @@ -32,7 +32,7 @@ Prerequisites: To add a group README: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. In the **Group README** section, select **Add README**. This action creates a new project `gitlab-profile` that contains the `README.md` file. 1. On the prompt for creating a README, select **Create and add README**. You're redirected to the Web IDE, where a README file is created. 1. In the Web IDE, edit and commit the `README.md` file. @@ -44,12 +44,12 @@ member with the Owner role. - As an administrator: 1. On the left sidebar, select **Search or go to** and find your group. - 1. Select **Manage > Members**. + 1. Select **Manage** > **Members**. 1. Give a different member the Owner role. 1. Refresh the page. You can now remove the Owner role from the original Owner. - As the current group's Owner: 1. On the left sidebar, select **Search or go to** and find your group. - 1. Select **Manage > Members**. + 1. Select **Manage** > **Members**. 1. Give a different member the Owner role. 1. Have the new Owner sign in and remove the Owner role from you. @@ -70,7 +70,7 @@ create a new group and transfer projects to it instead. To change your group path (group URL): 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Advanced** section. 1. Under **Change group URL**, enter a new name. 1. Select **Change group URL**. @@ -136,7 +136,7 @@ Prerequisites: To transfer a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Advanced** section. 1. Select **Transfer group**. 1. Select the group name in the drop down menu. @@ -149,7 +149,7 @@ You can disable all email notifications related to the group, which includes its To disable email notifications: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Clear the **Enable email notifications** checkbox. @@ -175,7 +175,7 @@ Prerequisites: To disable diff previews for all projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. Clear **Include diff previews**. 1. Select **Save changes**. @@ -202,7 +202,7 @@ The following group and project members receive notification emails about access You can enable notifications to inherited members of a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. Under **Expiry notification emails about group and project access tokens within this group should be sent to:**, select **All direct and inherited members of the group or project**. 1. Optional. Check the **Enforce for all subgroups** checkbox. @@ -227,7 +227,7 @@ GitLab sends multiple [expiry emails](settings/group_access_tokens.md#group-acce To enable additional triggers for these webhooks: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Select the **Extended Group Access Tokens Expiry Webhook execution** checkbox. 1. Select **Save changes**. @@ -245,7 +245,7 @@ These visual cues are particularly helpful for groups with many users. To disable group mentions: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Select **Group mentions are disabled**. 1. Select **Save changes**. @@ -277,7 +277,7 @@ Prerequisites: To prevent invitations to a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Select **Disable Group/Project members invitation**. 1. Select **Save changes**. @@ -294,7 +294,7 @@ To prevent invitations to a group: You can export a list of members in a group or subgroup as a CSV. 1. On the left sidebar, select **Search or go to** and find your group or subgroup. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. 1. Select **Export as CSV**. 1. After the CSV file has been generated, it is emailed as an attachment to the user that requested it. @@ -338,7 +338,7 @@ Prerequisites: To turn on restricted access: -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. Under **Seat control**, select **Restricted access**. @@ -396,7 +396,7 @@ To specify a user cap: 1. On the left sidebar, select **Search or go to** and find your group. You can set a cap on the top-level group only. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. From **Seat control**, select the **Set user cap** checkbox and enter the number of users in the field. 1. Select **Save changes**. @@ -417,7 +417,7 @@ Prerequisites: To remove the user cap: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. From **Seat control**, select **Open access**. 1. Select **Save changes**. @@ -438,7 +438,7 @@ Prerequisites: To approve members that are pending because they've exceeded the user cap: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > Usage Quotas**. +1. Select **Settings** > **Usage Quotas**. 1. On the **Seats** tab, under the alert, select **View pending approvals**. 1. For each member you want to approve, select **Approve**. @@ -493,7 +493,7 @@ For more information, see [group-level project templates](custom_project_templat To enable group file templates: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Templates** section. 1. Choose a project to act as the template repository. 1. Select **Save changes**. @@ -533,7 +533,7 @@ Prerequisites: To enable this setting: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Merge requests**. 1. Under **Merge checks**, select **Pipelines must succeed**. This setting also prevents merge requests from being merged if there is no pipeline. @@ -552,7 +552,7 @@ Prerequisites: To change this behavior: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Merge requests**. 1. Under **Merge checks**: - Select **Pipelines must succeed**. @@ -570,7 +570,7 @@ Prerequisites: To enable this setting: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Merge requests**. 1. Under **Merge checks**, select **All threads must be resolved**. 1. Select **Save changes**. @@ -591,7 +591,7 @@ that belong to the group. To view the merge request approval settings for a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Merge request approvals** section. 1. Select the settings you want. 1. Select **Save changes**. @@ -618,7 +618,7 @@ Changes to [group wikis](../project/wiki/group.md) do not appear in group activi You can view the most recent actions taken in a group, either in your browser or in an RSS feed: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Activity**. +1. Select **Manage** > **Activity**. To view the activity feed in Atom format, select the **RSS** ({{< icon name="rss" >}}) icon. diff --git a/doc/user/group/moderate_users.md b/doc/user/group/moderate_users.md index 89955433089269..b183d123425505 100644 --- a/doc/user/group/moderate_users.md +++ b/doc/user/group/moderate_users.md @@ -52,7 +52,7 @@ Prerequisites: To manually ban a user: 1. Go to the top-level group. -1. On the left sidebar, select **Manage > Members**. +1. On the left sidebar, select **Manage** > **Members**. 1. Next to the member you want to ban, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}). 1. From the dropdown list, select **Ban member**. @@ -70,7 +70,7 @@ Prerequisites: To unban a user: 1. Go to the top-level group. -1. On the left sidebar, select **Manage > Members**. +1. On the left sidebar, select **Manage** > **Members**. 1. Select the **Banned** tab. 1. For the account you want to unban, select **Unban**. @@ -109,7 +109,7 @@ Activity has not been recorded for members added before 2025-01-22. These member To turn on automatic dormant member removal: 1. On the left sidebar, select **Search or go to** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. Scroll to **Dormant members**. 1. Select the **Remove dormant members after a period of inactivity** checkbox. diff --git a/doc/user/group/reporting/git_abuse_rate_limit.md b/doc/user/group/reporting/git_abuse_rate_limit.md index e49b53f69bb140..b167e79caffb45 100644 --- a/doc/user/group/reporting/git_abuse_rate_limit.md +++ b/doc/user/group/reporting/git_abuse_rate_limit.md @@ -40,7 +40,7 @@ If automatic banning is enabled, an email notification is sent when a user is ab ## Configure Git abuse rate limiting -1. On the left sidebar, select **Settings > Reporting**. +1. On the left sidebar, select **Settings** > **Reporting**. 1. Update the Git abuse rate limit settings: 1. Enter a number in the **Number of repositories** field, greater than or equal to `0` and less than or equal to `10,000`. This number specifies the maximum amount of unique repositories a user can download in the specified time period before they're banned. When set to `0`, Git abuse rate limiting is disabled. 1. Enter a number in the **Reporting time period (seconds)** field, greater than or equal to `0` and less than or equal to `86,400` (10 days). This number specifies the time in seconds a user can download the maximum amount of repositories before they're banned. When set to `0`, Git abuse rate limiting is disabled. diff --git a/doc/user/group/repositories_analytics/_index.md b/doc/user/group/repositories_analytics/_index.md index d9164a3a2227a8..235e5cc257b569 100644 --- a/doc/user/group/repositories_analytics/_index.md +++ b/doc/user/group/repositories_analytics/_index.md @@ -31,7 +31,7 @@ Prerequisites: To view repository analytics for a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Analyze > Repository analytics**. +1. Select **Analyze** > **Repository analytics**. ## Coverage metrics diff --git a/doc/user/group/roadmap/_index.md b/doc/user/group/roadmap/_index.md index 8ac2da2cf0f441..d1bf3baed90214 100644 --- a/doc/user/group/roadmap/_index.md +++ b/doc/user/group/roadmap/_index.md @@ -33,7 +33,7 @@ The epic roadmap offers the following benefits: To view the roadmap in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Plan > Roadmap**. +1. Select **Plan** > **Roadmap**. The roadmap shows the epics and milestones in a group, one of its subgroups, or a project in one of the groups. diff --git a/doc/user/group/saml_sso/_index.md b/doc/user/group/saml_sso/_index.md index b317b6c7e25f0b..b236d08dcf8565 100644 --- a/doc/user/group/saml_sso/_index.md +++ b/doc/user/group/saml_sso/_index.md @@ -49,7 +49,7 @@ If you are having issues setting up your identity provider, see the To set up SSO with Azure as your identity provider: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. Note the information on this page. 1. Go to Azure, [create a non-gallery application](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/overview-application-gallery#create-your-own-application), and [configure SSO for an application](https://learn.microsoft.com/en-us/entra/identity/enterprise-apps/add-application-portal-setup-sso). The following GitLab settings correspond to the Azure fields. @@ -82,7 +82,7 @@ For more information, see the [Azure configuration example](example_saml_config. To set up Google Workspace as your identity provider: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. Note the information on this page. 1. Follow the instructions for [setting up SSO with Google as your identity provider](https://support.google.com/a/answer/6087519?hl=en). The following GitLab settings correspond to the Google Workspace fields. @@ -119,7 +119,7 @@ View a demo of [how to configure SAML with Google Workspaces and set up Group Sy To set up SSO with Okta as your identity provider: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. Note the information on this page. 1. Follow the instructions for [setting up a SAML application in Okta](https://developer.okta.com/docs/guides/build-sso-integration/saml2/main/). @@ -158,7 +158,7 @@ OneLogin supports its own [GitLab (SaaS) application](https://onelogin.service-n To set up OneLogin as your identity provider: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. Note the information on this page. 1. If you use the OneLogin generic [SAML Test Connector (Advanced)](https://onelogin.service-now.com/support?id=kb_article&sys_id=b2c19353dbde7b8024c780c74b9619fb&kb_category=93e869b0db185340d5505eea4b961934), @@ -186,7 +186,7 @@ For more information, see the [OneLogin configuration example](example_saml_conf To set up Keycloak as your identity provider: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. Note the information on this page. 1. Follow the instructions to [create a SAML client in Keycloack](https://www.keycloak.org/docs/latest/server_admin/index.html#_client-saml-configuration). @@ -253,7 +253,7 @@ To configure some identity providers, you need a GitLab metadata URL. To find this URL: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. Copy the provided **GitLab metadata URL**. 1. Follow your identity provider's documentation and paste the metadata URL when it's requested. @@ -297,7 +297,7 @@ If the **NameID** is configured with the email address, [change the **NameID** f After you set up your identity provider to work with GitLab, you must configure GitLab to use it for authentication: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. Complete the fields: - In the **Identity provider single sign-on URL** field, enter the SSO URL from your identity provider. - In the **Certificate fingerprint** field, enter the fingerprint for the SAML token signing certificate. @@ -356,7 +356,7 @@ To link SAML to your existing GitLab.com account: 1. Sign in to your GitLab.com account. [Reset your password](https://gitlab.com/users/password/new) if necessary. 1. Locate and visit the **GitLab single sign-on URL** for the group you're signing - in to. A group owner can find this on the group's **Settings > SAML SSO** page. + in to. A group owner can find this on the group's **Settings** > **SAML SSO** page. If the sign-in URL is configured, users can connect to the GitLab app from the identity provider. 1. Optional. Select the **Remember me** checkbox to stay signed in to GitLab for 2 weeks. You may still be asked to re-authenticate with your SAML provider more frequently. @@ -543,7 +543,7 @@ You can disable password authentication for all [enterprise users](../../enterpr To disable password authentication for enterprise users: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. Under **Configuration**, select **Disable password authentication for enterprise users**. 1. Select **Save changes**. diff --git a/doc/user/group/saml_sso/group_sync.md b/doc/user/group/saml_sso/group_sync.md index c118e0e0d0882b..6d8d18c6530804 100644 --- a/doc/user/group/saml_sso/group_sync.md +++ b/doc/user/group/saml_sso/group_sync.md @@ -261,7 +261,7 @@ Prerequisites: - Your GitLab Self-Managed instance must have configured SAML Group Sync. When SAML is enabled, users with the Owner role see a new menu -item in group **Settings > SAML Group Links**. +item in group **Settings** > **SAML Group Links**. - You can configure one or more **SAML Group Links** to map a SAML IdP group name to a GitLab role. - Members of the SAML IdP group are added as members of the GitLab @@ -397,7 +397,7 @@ To configure Azure AD: 1. To generate the credentials, select **Add**. 1. Copy the **Value** of the credential. This value is displayed only once, and you need it for the GitLab configuration. 1. In the left navigation, select **API permissions**. -1. Select **Microsoft Graph > Application permissions**. +1. Select **Microsoft Graph** > **Application permissions**. 1. Select the checkboxes **GroupMember.Read.All** and **User.Read.All**. 1. Select **Add permissions** to save. 1. Select **Grant admin consent for ``**, then on the confirmation dialog select **Yes**. The **Status** column for both permissions should change to a green check with **Granted for ``**. @@ -428,7 +428,7 @@ To configure Azure AD for a GitLab.com group: 1. On the left sidebar, select **Search or go to** and find your group. This group must be at the top level. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. Configure [SAML SSO for the group](_index.md). 1. In the **Microsoft Azure integration** section, select the **Enable Microsoft Azure integration for this group** checkbox. This section is only visible if SAML SSO is configured and enabled for the group. @@ -444,7 +444,7 @@ To configure for GitLab Self-Managed: 1. Configure [SAML SSO for the instance](../../../integration/saml.md). 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. In the **Microsoft Azure integration** section, select the **Enable Microsoft Azure integration for this group** checkbox. 1. Enter the **Tenant ID**, **Client ID**, and **Client secret** obtained earlier when configuring Azure Active Directory in the Azure Portal. 1. Optional. If using Azure AD for US Government or Azure AD China, enter the appropriate **Login API endpoint** and **Graph API endpoint**. The default values work for most organizations. @@ -489,6 +489,6 @@ Prerequisites: To lock memberships to SAML Group Links synchronization: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Visibility and access controls** section. 1. Select the **Lock memberships to SAML Group Links synchronization** checkbox. diff --git a/doc/user/group/saml_sso/scim_setup.md b/doc/user/group/saml_sso/scim_setup.md index fa0fa88ac5aa4e..6e246a3a2a6a39 100644 --- a/doc/user/group/saml_sso/scim_setup.md +++ b/doc/user/group/saml_sso/scim_setup.md @@ -36,7 +36,7 @@ Prerequisites: To configure GitLab SAML SSO SCIM: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. Select **Generate a SCIM token**. 1. For configuration of your identity provider, save the: - Token from the **Your SCIM token** field. diff --git a/doc/user/group/saml_sso/troubleshooting.md b/doc/user/group/saml_sso/troubleshooting.md index 01e581df3b57c2..44da8d344a24ae 100644 --- a/doc/user/group/saml_sso/troubleshooting.md +++ b/doc/user/group/saml_sso/troubleshooting.md @@ -517,7 +517,7 @@ This message might indicate that you must add or remove a domain from your domai To implement this workaround: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings** > **General**. +1. Select **Settings**** > ****General**. 1. Expand **Sign-up restrictions**. 1. Add or remove a domain as appropriate to **Allowed domains for sign-ups** and **Denied domains for sign-ups**. 1. Select **Save changes**. diff --git a/doc/user/group/settings/group_access_tokens.md b/doc/user/group/settings/group_access_tokens.md index 5728dc6dfdec67..81774445b10b83 100644 --- a/doc/user/group/settings/group_access_tokens.md +++ b/doc/user/group/settings/group_access_tokens.md @@ -73,7 +73,7 @@ The ability to create group access tokens without an expiry date was [deprecated To create a group access token: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > Access tokens**. +1. Select **Settings** > **Access tokens**. 1. Select **Add new token**. 1. In **Token name**, enter a name. The token name is visible to any user with permissions to view the group. 1. Optional. In **Token description**, enter a description for the token. @@ -158,7 +158,7 @@ Tokens that belong to [an active token family](../../../api/personal_access_toke To revoke or rotate a group access token: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > Access tokens**. +1. Select **Settings** > **Access tokens**. 1. For the relevant token, select **Revoke** ({{< icon name="remove" >}}) or **Rotate** ({{< icon name="retry" >}}). 1. On the confirmation dialog, select **Revoke** or **Rotate**. @@ -198,7 +198,7 @@ To restrict the creation of group access tokens: 1. On the left sidebar, select **Search or go to** and find your group. This group must be at the top level. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. Under **Permissions**, clear the **Users can create project access tokens and group access tokens in this group** checkbox. 1. Select **Save changes**. diff --git a/doc/user/group/ssh_certificates.md b/doc/user/group/ssh_certificates.md index d3ec4eb3e728f6..cbca9708590e4f 100644 --- a/doc/user/group/ssh_certificates.md +++ b/doc/user/group/ssh_certificates.md @@ -150,7 +150,7 @@ Prerequisites: To enforce using SSH certificates: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Permissions and group features** section. 1. Select the **Enforce SSH Certificates** checkbox. 1. Select **Save changes**. diff --git a/doc/user/group/subgroups/_index.md b/doc/user/group/subgroups/_index.md index 8c7e337d896670..4a51ae392f08ec 100644 --- a/doc/user/group/subgroups/_index.md +++ b/doc/user/group/subgroups/_index.md @@ -110,13 +110,13 @@ To change who can create subgroups on a group: - As a user with the Owner role on the group: 1. On the left sidebar, select **Search or go to** and find your group. - 1. Select **Settings > General**. + 1. Select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. From **Roles allowed to create subgroups**, select an option. 1. Select **Save changes**. - As an administrator: 1. On the left sidebar, at the bottom, select **Admin**. - 1. On the left sidebar, select **Overview > Groups** and find your group. + 1. On the left sidebar, select **Overview** > **Groups** and find your group. 1. In the group's row, select **Edit**. 1. From the **Allowed to create subgroups** dropdown list, select an option. 1. Select **Save changes**. @@ -181,7 +181,7 @@ Group permissions for a member can be changed only by: To see if a member has inherited the permissions from a parent group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Members**. +1. Select **Manage** > **Members**. The member's inheritance is displayed in the **Source** column. Members list for an example subgroup **Four**: diff --git a/doc/user/group/value_stream_analytics/_index.md b/doc/user/group/value_stream_analytics/_index.md index f938c94c8f3fd9..42e8b349ad493d 100644 --- a/doc/user/group/value_stream_analytics/_index.md +++ b/doc/user/group/value_stream_analytics/_index.md @@ -297,7 +297,7 @@ Prerequisites: To view value stream analytics for your group or project: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Value stream analytics**. +1. Select **Analyze** > **Value stream analytics**. 1. To view metrics for a particular stage, select a stage below the **Filter results** text box. 1. Optional. Filter the results: 1. Select the **Filter results** text box. @@ -392,7 +392,7 @@ Prerequisites: To view lifecycle metrics: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Value stream analytics**. +1. Select **Analyze** > **Value stream analytics**. Lifecycle metrics display below the **Filter results** text box. 1. Optional. Filter the results: 1. Select the **Filter results** text box. @@ -406,7 +406,7 @@ To view lifecycle metrics: To view the [Value Streams Dashboard](../../analytics/value_streams_dashboard.md) and [DORA metrics](../../analytics/dora_metrics.md): 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Value stream analytics**. +1. Select **Analyze** > **Value stream analytics**. 1. Below the **Filter results** text box, in the **Lifecycle metrics** row, select **Value Streams Dashboard / DORA**. 1. Optional. To open the new page, append this path `/analytics/dashboards/value_streams_dashboard` to the group URL (for example, `https://gitlab.com/groups/gitlab-org/-/analytics/dashboards/value_streams_dashboard`). @@ -418,7 +418,7 @@ Value stream analytics shows the median time spent by issues or merge requests i To view the median time spent in each stage by a group: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Value stream analytics**. +1. Select **Analyze** > **Value stream analytics**. 1. Optional. Filter the results: 1. Select the **Filter results** text box. 1. Select a parameter. @@ -451,7 +451,7 @@ The chart uses the global page filters to display data based on the selected gro To view tasks by type: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Analyze > Value stream analytics**. +1. Select **Analyze** > **Value stream analytics**. 1. Below the **Filter results** text box, select **Overview**. The **Tasks by type** chart displays below the **Total time** chart. 1. Optional. To filter the tasks by type, select **Settings** ({{< icon name="settings" >}}), then **Issues** or **Merge Requests**. 1. Optional. To filter the tasks by label, select **Settings** ({{< icon name="settings" >}}), then one or more labels. By default the top group labels (maximum 10) are selected. You can select a maximum of 15 labels. @@ -477,7 +477,7 @@ To view tasks by type: To create a value stream with default stages: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Value Stream analytics**. +1. Select **Analyze** > **Value Stream analytics**. 1. Select **New Value Stream**. 1. Enter a name for the value stream. 1. Select **Create from default template**. @@ -500,7 +500,7 @@ If you have recently upgraded to GitLab Premium, it can take up to 30 minutes fo To create a value stream with custom stages: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Value Stream analytics**. +1. Select **Analyze** > **Value Stream analytics**. 1. Select **New value stream**. 1. For each stage: - Enter a name for the stage. @@ -557,7 +557,7 @@ The first value stream uses standard timestamp-based events for defining the sta After you create a value stream, you can customize it to suit your purposes. To edit a value stream: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Value stream analytics**. +1. Select **Analyze** > **Value stream analytics**. 1. From the value stream dropdown list, select the value stream you want to edit. 1. Next to the value stream dropdown list, select **Edit**. 1. Optional: @@ -581,7 +581,7 @@ After you create a value stream, you can customize it to suit your purposes. To To delete a custom value stream: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Value stream analytics**. +1. Select **Analyze** > **Value stream analytics**. 1. From the value stream dropdown list, select the value stream you want to delete, then **Delete (name of value stream)**. 1. To confirm, select **Delete**. @@ -598,7 +598,7 @@ The **Total time chart** shows the average number of days it takes for developme The chart shows data for the last 500 workflow items. 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Value stream analytics**. +1. Select **Analyze** > **Value stream analytics**. 1. Above the **Filter results** box, select a stage: - To view a summary of the cycle time for all stages, select **Overview**. - To view the cycle time for specific stage, select a stage. diff --git a/doc/user/okrs.md b/doc/user/okrs.md index 53dca7ada8ccf1..727df05abd5899 100644 --- a/doc/user/okrs.md +++ b/doc/user/okrs.md @@ -69,7 +69,7 @@ To learn how to create better OKRs and how we use them at GitLab, see the To create an objective: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**. +1. Select **Plan** > **Issues**. 1. In the upper-right corner, next to **New issue**, select the down arrow {{< icon name="chevron-lg-down" >}} and then select **New objective**. 1. Select **New objective** again. 1. Enter the objective title. @@ -82,7 +82,7 @@ To create a key result, [add it as a child](#add-a-child-key-result) to an exist To view an objective: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**. +1. Select **Plan** > **Issues**. 1. [Filter the list of issues](project/issues/managing_issues.md#filter-the-list-of-issues) for `Type = objective`. 1. Select the title of an objective from the list. @@ -92,7 +92,7 @@ To view an objective: To view a key result: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**. +1. Select **Plan** > **Issues**. 1. [Filter the list of issues](project/issues/managing_issues.md#filter-the-list-of-issues) for `Type = key_result`. 1. Select the title of a key result from the list. @@ -276,7 +276,7 @@ Prerequisites: To set progress of an objective or key result: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**. +1. Select **Plan** > **Issues**. 1. [Filter the list of issues](project/issues/managing_issues.md#filter-the-list-of-issues) for `Type = objective` or `Type = key result` and select your item. 1. Next to **Progress**, select the text box. @@ -357,7 +357,7 @@ Prerequisites: To convert an OKR into another item type: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue list, find your objective or key result and select it. 1. In the upper-right corner, select **More actions** ({{< icon name="ellipsis_v" >}}), then select **Change type**. 1. Select the desired item type. @@ -380,7 +380,7 @@ To refer to an objective or key result elsewhere in GitLab, you can use its full To copy the objective or key result reference to your clipboard: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your objective or key result to view it. +1. Select **Plan** > **Issues**, then select your objective or key result to view it. 1. In the upper-right corner, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}), then select **Copy Reference**. You can now paste the reference into another description or comment. @@ -404,7 +404,7 @@ For more information about creating comments by sending an email and the necessa To copy the objective's or key result's email address: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the upper-right corner, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}), then select **Copy objective email address** or **Copy key result email address**. ## Close an OKR diff --git a/doc/user/organization/_index.md b/doc/user/organization/_index.md index a9271854b239a2..34a0c320ef8a54 100644 --- a/doc/user/organization/_index.md +++ b/doc/user/organization/_index.md @@ -61,7 +61,7 @@ Support for only private organizations is proposed for [cells 1.0](https://gitla ## Edit an organization's name 1. On the left sidebar, select **Organizations** and find the organization you want to edit. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. In the **Organization name** text box, edit the name. 1. In the **Organization description** text box, edit the description. Supports a [limited subset of Markdown](#supported-markdown-for-organization-description). 1. In the **Organization avatar** field, if an avatar is: @@ -72,7 +72,7 @@ Support for only private organizations is proposed for [cells 1.0](https://gitla ## Change an organization's URL 1. On the left sidebar, select **Organizations** and find the organization whose URL you want to change. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Advanced** section. 1. In the **Organization URL** text box, edit the URL. 1. Select **Change organization URL**. @@ -86,7 +86,7 @@ Support for only private organizations is proposed for [cells 1.0](https://gitla {{< /alert >}} 1. On the left sidebar, select **Organizations** and find your organization. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Visibility** section. ## Switch organizations @@ -105,7 +105,7 @@ To switch organizations: ## Manage groups and projects 1. On the left sidebar, select **Organizations** and find the organization you want to manage. -1. Select **Manage > Groups and projects**. +1. Select **Manage** > **Groups and projects**. 1. Optional. Filter the results: - To search for specific groups or projects, in the search box enter your search term (minimum three characters). - To view only groups or projects, from the **Display** dropdown list select an option. @@ -114,7 +114,7 @@ To switch organizations: ## Create a group in an organization 1. On the left sidebar, select **Organizations** and find the organization you want to create a group in. -1. Select **Manage > Groups and projects**. +1. Select **Manage** > **Groups and projects**. 1. Select **New group**. 1. In the **Group name** text box, enter the name of the group. For a list of words that cannot be used as group names, see [reserved names](../reserved_names.md). @@ -125,7 +125,7 @@ To switch organizations: ## View users 1. On the left sidebar, select **Organizations** and find the organization you want to view. -1. Select **Manage > Users**. +1. Select **Manage** > **Users**. ## Change a user's role @@ -136,7 +136,7 @@ Prerequisites: To change a user's role: 1. On the left sidebar, select **Organizations** and find the organization you want to manage. -1. Select **Manage > Users**. +1. Select **Manage** > **Users**. 1. Find the user whose role you want to update. 1. From the **Organization role** dropdown list, select a role. diff --git a/doc/user/permissions.md b/doc/user/permissions.md index 9cf7fc7b1380dd..124becbf653efd 100644 --- a/doc/user/permissions.md +++ b/doc/user/permissions.md @@ -850,7 +850,7 @@ to control access to groups and projects in the group hierarchy. You can set the Minimal Access for members automatically added to the top-level group through SSO. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > SAML SSO**. +1. Select **Settings** > **SAML SSO**. 1. From the **Default membership role** dropdown list, select **Minimal Access**. 1. Select **Save changes**. diff --git a/doc/user/project/badges.md b/doc/user/project/badges.md index 7ce5d70fb1d3eb..e508c526034a83 100644 --- a/doc/user/project/badges.md +++ b/doc/user/project/badges.md @@ -152,7 +152,7 @@ A common project badge presents the GitLab CI pipeline status. To add this badge to a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Badges**. 1. Under **Name**, enter _Pipeline Status_. 1. Under **Link**, enter the following URL: @@ -185,7 +185,7 @@ If you need individual badges for each project, either: To view badges available in a project or group: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Badges**. ## Add a badge @@ -193,7 +193,7 @@ To view badges available in a project or group: To add a new badge to a project or group: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Badges**. 1. Select **Add badge**. 1. In the **Name** text box, enter the name of your badge. @@ -277,7 +277,7 @@ To add a new badge with a custom image to a group or project: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Badges**. 1. Under **Name**, enter the name for the badge. 1. Under **Link**, enter the URL that the badge should point to. @@ -293,7 +293,7 @@ To learn how to use custom images generated through a pipeline, see the document To edit a badge in a project or group: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Badges**. 1. Next to the badge you want to edit, select **Edit** ({{< icon name="pencil" >}}). 1. Edit the **Name**, **Link**, or **Badge image URL**. @@ -304,7 +304,7 @@ To edit a badge in a project or group: To delete a badge in a project or group: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Badges**. 1. Next to the badge you want to delete, select **Delete** ({{< icon name="remove" >}}). 1. On the confirmation dialog, select **Delete badge**. diff --git a/doc/user/project/canary_deployments.md b/doc/user/project/canary_deployments.md index 4aa47fbe00d467..4657aabe52835e 100644 --- a/doc/user/project/canary_deployments.md +++ b/doc/user/project/canary_deployments.md @@ -94,7 +94,7 @@ Any other track label is considered `canary` (temporary). This allows GitLab to discover whether a deployment is stable or canary (temporary). After you configure the deploy boards, and the pipeline runs at least once, -Go to the environments page under **Pipelines > Environments**. +Go to the environments page under **Pipelines** > **Environments**. As the pipeline executes, deploy boards clearly mark canary pods, enabling quick and clear insight into the status of each environment and deployment. @@ -129,7 +129,7 @@ or by sending requests to the [GraphQL API](../../api/graphql/getting_started.md To use your [deploy board](deploy_boards.md): -1. Go to **Operate > Environments** for your project. +1. Go to **Operate** > **Environments** for your project. 1. Set the new weight with the dropdown list on the right side. 1. Confirm your selection. diff --git a/doc/user/project/code_intelligence.md b/doc/user/project/code_intelligence.md index bf43a961638c69..f8ab8c991d7115 100644 --- a/doc/user/project/code_intelligence.md +++ b/doc/user/project/code_intelligence.md @@ -164,7 +164,7 @@ can change this value. After the job succeeds, browse your repository to see code intelligence information: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Repository**. +1. Select **Code** > **Repository**. 1. Go to the file in your repository. If you know the filename, either: - Enter the `/~` keyboard shortcut to open the file finder, and enter the file's name. - In the upper right, select **Find file**. @@ -179,7 +179,7 @@ After the job succeeds, browse your repository to see code intelligence informat Use code intelligence to see all uses of an object: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Repository**. +1. Select **Code** > **Repository**. 1. Go to the file in your repository. If you know the filename, either: - Enter the `/~` keyboard shortcut to open the file finder, and enter the file's name. - In the upper right, select **Find file**. diff --git a/doc/user/project/deploy_boards.md b/doc/user/project/deploy_boards.md index cd0f6eee0511ea..b69e8e64506908 100644 --- a/doc/user/project/deploy_boards.md +++ b/doc/user/project/deploy_boards.md @@ -128,7 +128,7 @@ To display the deploy boards for a specific [environment](../../ci/environments/ ![deploy boards Kubernetes Label](img/deploy_boards_kubernetes_label_v11_9.png) Once all of these previous instructions are set up and the pipeline has run at least once, -go to the environments page under **Operate > Environments**. +go to the environments page under **Operate** > **Environments**. Deploy boards are visible by default. You can explicitly select the triangle next to their respective environment name to hide them. diff --git a/doc/user/project/description_templates.md b/doc/user/project/description_templates.md index 9a373700b098d5..57559b85f5c9b2 100644 --- a/doc/user/project/description_templates.md +++ b/doc/user/project/description_templates.md @@ -58,7 +58,7 @@ Create a new description template as a Markdown (`.md`) file inside the `.gitlab To create a work item description template: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Repository**. +1. Select **Code** > **Repository**. 1. Next to the default branch, select {{< icon name="plus" >}}. 1. Select **New file**. 1. Next to the default branch, in the **File name** text box, enter `.gitlab/issue_templates/mytemplate.md`, @@ -81,7 +81,7 @@ that depend on the contents of commit messages and branch names. To create a merge request description template for a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Repository**. +1. Select **Code** > **Repository**. 1. Next to the default branch, select {{< icon name="plus" >}}. 1. Select **New file**. 1. Next to the default branch, in the **File name** text box, enter `.gitlab/merge_request_templates/mytemplate.md`, @@ -179,7 +179,7 @@ Prerequisites: To re-use templates [you've created](description_templates.md#create-a-description-template): 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Templates**. 1. From the dropdown list, select your template project as the template repository at group level. 1. Select **Save changes**. @@ -197,7 +197,7 @@ entered in the template. Prerequisites: -- On your project's left sidebar, select **Settings > General** and expand **Visibility, project features, permissions**. +- On your project's left sidebar, select **Settings** > **General** and expand **Visibility, project features, permissions**. Ensure issues or merge requests are set to either **Everyone with access** or **Only Project Members**. To set a default description template for merge requests, either: @@ -208,7 +208,7 @@ To set a default description template for merge requests, either: - Users on GitLab Premium and Ultimate: set the default template in project settings: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Settings > Merge requests**. + 1. Select **Settings** > **Merge requests**. 1. In the **Default description template for merge requests** section, fill in the text area. 1. Select **Save changes**. @@ -220,7 +220,7 @@ To set a default description template for issues, either: - Users on GitLab Premium and Ultimate: set the default template in project settings: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Settings > General**. + 1. Select **Settings** > **General**. 1. Expand **Default description template for issues**. 1. Fill in the text area. 1. Select **Save changes**. diff --git a/doc/user/project/file_lock.md b/doc/user/project/file_lock.md index c2d146063909c4..9cde4a3d5109d7 100644 --- a/doc/user/project/file_lock.md +++ b/doc/user/project/file_lock.md @@ -104,7 +104,7 @@ Prerequisites: To view locked files: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Locked files**. +1. Select **Code** > **Locked files**. The **Locked files** page displays all files locked with either Git LFS exclusive locks or the GitLab UI. @@ -132,7 +132,7 @@ To remove a lock: {{< tab title="From the Locked file page" >}} 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Locked files**. +1. Select **Code** > **Locked files**. 1. To the right of the file you want to unlock, select **Unlock**. 1. On the confirmation dialog, select **OK**. diff --git a/doc/user/project/insights/_index.md b/doc/user/project/insights/_index.md index 09f9c4fec3cf89..5ae731bbff757c 100644 --- a/doc/user/project/insights/_index.md +++ b/doc/user/project/insights/_index.md @@ -30,7 +30,7 @@ Prerequisites: To view insights for a project or group: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Analyze > Insights**. +1. Select **Analyze** > **Insights**. 1. To view a report, from the **Select report** dropdown list, select the report you want to view. ### Access insights reports with deep links @@ -128,7 +128,7 @@ To configure group insights: 1. In a project that belongs to your group, [create a `.gitlab/insights.yml` file](#configure-project-insights). 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > Analytics**. +1. Select **Settings** > **Analytics**. 1. In the **Insights** section, select the project that contains your `.gitlab/insights.yml` configuration file. 1. Select **Save changes**. diff --git a/doc/user/project/issue_board.md b/doc/user/project/issue_board.md index c5433fc7b8c7fc..b3618dd6f9b6b6 100644 --- a/doc/user/project/issue_board.md +++ b/doc/user/project/issue_board.md @@ -573,7 +573,7 @@ You can create a new list between two existing lists or at the right of an issue To create a new list between two lists: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issue boards**. +1. Select **Plan** > **Issue boards**. 1. Hover or move keyboard focus between two lists. 1. Select **New list**. The new list panel opens. diff --git a/doc/user/project/labels.md b/doc/user/project/labels.md index fbc680033e6bb8..205d9c919910b9 100644 --- a/doc/user/project/labels.md +++ b/doc/user/project/labels.md @@ -78,7 +78,7 @@ You can also assign and unassign labels with [quick actions](quick_actions.md): To view the **project's labels**: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. Or: @@ -95,7 +95,7 @@ project or group path where it was created. To view the **group's labels**: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. Or: @@ -123,7 +123,7 @@ Prerequisites: To create a project label: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. 1. Select **New label**. 1. In the **Title** field, enter a short, descriptive name for the label. You can also use this field to create [scoped, mutually exclusive labels](#scoped-labels). @@ -163,7 +163,7 @@ To do so: To create a group label: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. 1. Select **New label**. 1. In the **Title** field, enter a short, descriptive name for the label. You can also use this field to create [scoped, mutually exclusive labels](#scoped-labels). @@ -222,7 +222,7 @@ Prerequisites: To edit a **project** label: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. 1. Next to the label you want to edit, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}), and then select **Edit**. 1. Select **Save changes**. @@ -231,7 +231,7 @@ To edit a **project** label: To edit a **group** label: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. 1. Next to the label you want to edit, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}), and then select **Edit**. 1. Select **Save changes**. @@ -259,7 +259,7 @@ Prerequisites: To delete a **project** label: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. 1. Next to the **Subscribe** button, select ({{< icon name="ellipsis_v" >}}), and then select **Delete**. ### Delete a group label @@ -267,7 +267,7 @@ To delete a **project** label: To delete a **group** label: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. 1. Either: - Next to the **Subscribe** button, select ({{< icon name="ellipsis_v" >}}). @@ -304,7 +304,7 @@ Prerequisites: To promote a project label to a group label: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. 1. Next to the **Subscribe** button, select the three dots ({{< icon name="ellipsis_v" >}}) and select **Promote to group label**. @@ -367,7 +367,7 @@ Prerequisites: To add the default labels to the project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. 1. Select **Generate a default set of labels**. The following labels are created: @@ -527,7 +527,7 @@ Prerequisites: To prioritize a label: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. 1. Next to a label you want to prioritize, select the star ({{< icon name="star-o" >}}). ![Labels prioritized](img/labels_prioritized_v13_5.png) @@ -583,7 +583,7 @@ After you set a label as locked, nobody can undo it or delete the label. To set a label to get locked on merge: 1. On the left sidebar, select **Search or go to** and find your group or project. -1. Select **Manage > Labels**. +1. Select **Manage** > **Labels**. 1. Next to the label you want to edit, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}), and then select **Edit**. 1. Select the **Lock label after a merge request is merged** checkbox. 1. Select **Save changes**. diff --git a/doc/user/project/project_topics.md b/doc/user/project/project_topics.md index 2e77ea5d5bec94..1990a283f4070b 100644 --- a/doc/user/project/project_topics.md +++ b/doc/user/project/project_topics.md @@ -89,7 +89,7 @@ The URL of the result contains a feed token and the list of projects that have t To assign topics to a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings** > **General**. +1. Select **Settings**** > ****General**. 1. In the **Topics** text box, enter the project topics. Popular topics are suggested as you type. 1. Select **Save changes**. diff --git a/doc/user/project/protected_tags.md b/doc/user/project/protected_tags.md index a50c9451245f9f..6acbe236b23061 100644 --- a/doc/user/project/protected_tags.md +++ b/doc/user/project/protected_tags.md @@ -38,7 +38,7 @@ Prerequisites: - You must have at least the Maintainer role for the project. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Protected tags**. 1. Select **Add new**. 1. To protect a single tag, select **Tag**, then choose your tag from the dropdown list. @@ -64,7 +64,7 @@ The protected tag (or wildcard) displays in the **Protected tags** list. To set the members of a group or subgroup as Allowed to create protected tags: 1. On the left sidebar, select **Search or go** to and find your project. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Protected tags**. 1. Add groups to the following field: @@ -184,7 +184,7 @@ Prerequisites: To allow a deploy key to create a protected tag: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Protected tags**. 1. From the **Tag** dropdown list, select the tag you want to protect. 1. From the **Allowed to create** list, select the deploy key. @@ -212,7 +212,7 @@ Prerequisites: To do this: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Tags**. +1. Select **Code** > **Tags**. 1. Next to the tag you want to delete, select **Delete** ({{< icon name="remove" >}}). 1. On the confirmation dialog, enter the tag name and select **Yes, delete protected tag**. diff --git a/doc/user/project/releases/_index.md b/doc/user/project/releases/_index.md index 8f7265d34bf457..ac36c8b86f3c0e 100644 --- a/doc/user/project/releases/_index.md +++ b/doc/user/project/releases/_index.md @@ -43,7 +43,7 @@ When you create a release, or after, you can: To view a list of releases: -- On the left sidebar, select **Deploy > Releases**, or +- On the left sidebar, select **Deploy** > **Releases**, or - On the project's overview page, if at least one release exists, select the number of releases. @@ -95,7 +95,7 @@ GitLab provides an RSS feed of a project's releases, in Atom format. To view the 1. For projects you are a member of: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Deploy > Releases**. + 1. Select **Deploy** > **Releases**. 1. For all projects: 1. Go to the **Project overview** page. 1. On the right sidebar, select **Releases** ({{< icon name="rocket-launch" >}}). @@ -119,7 +119,7 @@ Prerequisites: To create a release in the Releases page: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Deploy > Releases** and select **New release**. +1. Select **Deploy** > **Releases** and select **New release**. 1. From the [**Tag name**](release_fields.md#tag-name) dropdown list, either: - Select an existing Git tag. Selecting an existing tag that is already associated with a release results in a validation error. @@ -275,7 +275,7 @@ Prerequisites: In the UI: -1. On the left sidebar, select **Deploy > Releases**. +1. On the left sidebar, select **Deploy** > **Releases**. 1. In the upper-right corner of the release you want to modify, select **Edit this release** (the pencil icon). 1. On the **Edit Release** page, change the release's details. 1. Select **Save changes**. @@ -302,7 +302,7 @@ To delete a release, use either the In the UI: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Deploy > Releases**. +1. Select **Deploy** > **Releases**. 1. In the upper-right corner of the release you want to delete, select **Edit this release** ({{< icon name="pencil" >}}). 1. On the **Edit Release** page, select **Delete**. @@ -319,17 +319,17 @@ the [Releases API](../../../api/releases/_index.md#create-a-release). In the user interface, to associate milestones to a release: -1. On the left sidebar, select **Deploy > Releases**. +1. On the left sidebar, select **Deploy** > **Releases**. 1. In the upper-right corner of the release you want to modify, select **Edit this release** (the pencil icon). 1. From the **Milestones** list, select each milestone you want to associate. You can select multiple milestones. 1. Select **Save changes**. -On the **Deploy > Releases** page, the **Milestone** is listed in the top +On the **Deploy** > **Releases** page, the **Milestone** is listed in the top section, along with statistics about the issues in the milestones. ![A Release with one associated milestone](img/release_with_milestone_v12_9.png) -Releases are also visible on the **Plan > Milestones** page, and when you select a milestone +Releases are also visible on the **Plan** > **Milestones** page, and when you select a milestone on this page. Here is an example of milestones with no releases, one release, and two releases. diff --git a/doc/user/project/repository/_index.md b/doc/user/project/repository/_index.md index c196505436d357..2e77920e2e5cc8 100644 --- a/doc/user/project/repository/_index.md +++ b/doc/user/project/repository/_index.md @@ -148,7 +148,7 @@ For more information, see [Contributor analytics](../../analytics/contributor_an A repository graph displays a visual history of the repository network, including branches and merges. This graph helps you see the flow of changes in the repository. -To view the repository history graph, go to your project's **Code > Repository graph**. +To view the repository history graph, go to your project's **Code** > **Repository graph**. ![A graph showing the flow of commits in a repository.](img/repo_graph_v17_9.png) diff --git a/doc/user/project/repository/branches/default.md b/doc/user/project/repository/branches/default.md index 56febaa9e99639..cc9f719a783ee1 100644 --- a/doc/user/project/repository/branches/default.md +++ b/doc/user/project/repository/branches/default.md @@ -47,7 +47,7 @@ Prerequisites: To update the default branch for an individual [project](../../_index.md): 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Branch defaults**. For **Default branch**, select a new default branch. 1. Optional. Select the **Auto-close referenced issues on default branch** checkbox to close issues when a merge request @@ -71,7 +71,7 @@ customize the initial branch for projects hosted on that instance. Individual groups and subgroups can override the instance default for their projects. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Default branch**. 1. For **Initial default branch name**, select a new default branch. 1. Select **Save changes**. @@ -89,7 +89,7 @@ Prerequisites: To change the default branch name for new projects in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Default branch**. 1. For **Initial default branch name**, select a new default branch. 1. Select **Save changes**. @@ -151,7 +151,7 @@ Administrators of GitLab Self-Managed instances can customize the initial defaul groups and subgroups can override the instance default setting for their projects. 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Default branch**. 1. Select [**Initial default branch protection**](#protect-initial-default-branches). 1. To allow group owners to override the instance's default branch protection, select @@ -173,7 +173,7 @@ on a per-group basis. In disable this privilege for group owners, enforcing the protection rule set for the instance: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand the **Default branch** section. 1. Clear the **Allow owners to manage default branch protection per group** checkbox. 1. Select **Save changes**. @@ -200,7 +200,7 @@ on a per-group basis. In which locks this setting for group owners. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Default branch**. 1. Select [**Initial default branch protection**](#protect-initial-default-branches). 1. Select **Save changes**. diff --git a/doc/user/project/repository/code_suggestions/_index.md b/doc/user/project/repository/code_suggestions/_index.md index bec179759b2989..472888a6a0ea6c 100644 --- a/doc/user/project/repository/code_suggestions/_index.md +++ b/doc/user/project/repository/code_suggestions/_index.md @@ -351,7 +351,7 @@ You can disable prompt caching for top-level groups in the GitLab Duo settings. On GitLab.com: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > GitLab Duo**. +1. Select **Settings** > **GitLab Duo**. 1. Select **Change configuration**. 1. Disable the **Prompt caching** toggle. 1. Select **Save changes**. @@ -359,7 +359,7 @@ On GitLab.com: On GitLab Self-Managed: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **GitLab Duo features**. 1. Disable the **Prompt caching** toggle. 1. Select **Save changes**. @@ -407,7 +407,7 @@ Prerequisites: {{< tab title="In 17.4 and later" >}} 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **GitLab Duo features**. 1. Under **Connection method**, choose an option: - To minimize latency for code completion requests, select **Direct connections**. @@ -419,7 +419,7 @@ Prerequisites: {{< tab title="In 17.3 and earlier" >}} 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **AI-native features**. 1. Choose an option: - To enable direct connections and minimize latency for code completion requests, clear the **Disable direct connections for code suggestions** checkbox. diff --git a/doc/user/project/repository/code_suggestions/set_up.md b/doc/user/project/repository/code_suggestions/set_up.md index 40f0c846335306..6a1ceb5e7df6f8 100644 --- a/doc/user/project/repository/code_suggestions/set_up.md +++ b/doc/user/project/repository/code_suggestions/set_up.md @@ -105,7 +105,7 @@ If your IDE detects a non-trusted SSL certificate: To review certificates you've already accepted: 1. In your IDE, on the top bar, select your IDE name, then select **Settings**. -1. On the left sidebar, select **Tools > Server Certificates**. +1. On the left sidebar, select **Tools** > **Server Certificates**. 1. Select [**Server Certificates**](https://www.jetbrains.com/help/idea/settings-tools-server-certificates.html). 1. Select a certificate to view it. diff --git a/doc/user/project/repository/code_suggestions/supported_extensions.md b/doc/user/project/repository/code_suggestions/supported_extensions.md index 17a75e27444dd4..b5a7ca48c0d197 100644 --- a/doc/user/project/repository/code_suggestions/supported_extensions.md +++ b/doc/user/project/repository/code_suggestions/supported_extensions.md @@ -160,8 +160,8 @@ To do this: [language identifiers](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocumentItem). You need the identifier for your languages in a later step. 1. In your IDE, on the top bar, select your IDE name, then select **Settings**. -1. On the left sidebar, select **Tools > GitLab Duo**. -1. Under **Code Suggestions Enabled Languages > Additional languages**, add the identifier for each language +1. On the left sidebar, select **Tools** > **GitLab Duo**. +1. Under **Code Suggestions Enabled Languages** > **Additional languages**, add the identifier for each language you want to support. Identifiers should be in lowercase, like `html`. Separate multiple identifiers with commas, like `html,powershell,latex`, and don't add leading periods to each identifier. 1. Select **OK**. diff --git a/doc/user/project/repository/code_suggestions/troubleshooting.md b/doc/user/project/repository/code_suggestions/troubleshooting.md index 098d6b455f141e..08586456039f4c 100644 --- a/doc/user/project/repository/code_suggestions/troubleshooting.md +++ b/doc/user/project/repository/code_suggestions/troubleshooting.md @@ -83,9 +83,9 @@ For non-Code Suggestions troubleshooting for VS Code, see [Troubleshooting the G If you are on GitLab Self-Managed, ensure that Code Suggestions for the [GitLab Web IDE](../../web_ide/_index.md) is enabled. The same settings apply to VS Code as local IDE. -1. On the left sidebar, select **Extensions > GitLab Workflow**. +1. On the left sidebar, select **Extensions** > **GitLab Workflow**. 1. Select **Settings** ({{< icon name="settings" >}}), and then select **Extension Settings**. -1. In **GitLab > Duo Code Suggestions**, select the **GitLab Duo Code Suggestions** +1. In **GitLab** > **Duo Code Suggestions**, select the **GitLab Duo Code Suggestions** checkbox. #### View Code Suggestions logs @@ -93,7 +93,7 @@ If you are on GitLab Self-Managed, ensure that Code Suggestions for the [GitLab If Code Suggestions are enabled for the IDE, but suggestions are still not displayed: 1. In your IDE, in the GitLab Workflow **Extension Settings**, enable **GitLab: Debug**. -1. On the top menu, select **View > Output** to open the bottom panel, then either: +1. On the top menu, select **View** > **Output** to open the bottom panel, then either: - In the command palette, select `GitLab: Show Extension Logs`. - In the bottom panel, on the right, select the dropdown list to filter the logs. Select **GitLab Workflow**. 1. In the GitLab Workflow **Extension Settings**, clear and re-select the **GitLab Duo Code Suggestions** checkbox. @@ -160,9 +160,9 @@ For non-Code Suggestions troubleshooting for JetBrains IDEs, see [JetBrains trou ### Suggestions not displayed in JetBrains IDEs -1. From the **Tools > GitLab Duo** menu, select **Verify setup**. Make sure the health check passes. +1. From the **Tools** > **GitLab Duo** menu, select **Verify setup**. Make sure the health check passes. 1. Verify that your JetBrains IDE natively supports the language of the file you are - working on. Go to **Settings** > **Languages & Frameworks** to see the full list of + working on. Go to **Settings**** > ****Languages & Frameworks** to see the full list of languages and frameworks supported by your JetBrains IDE. ### Error: `unable to find valid certification path to requested target` @@ -176,7 +176,7 @@ This error occurs when the provided connection instance URL and authentication t GitLab Language Server process are invalid. To re-enable Code Suggestions: 1. In your IDE, on the top bar, select your IDE name, then select **Settings**. -1. On the left sidebar, select **Tools > GitLab Duo**. +1. On the left sidebar, select **Tools** > **GitLab Duo**. 1. Under **Connection**, select **Verify setup**. 1. Update your **Connection** details as needed. 1. Select **Verify setup**, and confirm that authentication succeeds. @@ -223,8 +223,8 @@ To fix this problem, install the IntelliCode component: ### Suggestions not displayed in Microsoft Visual Studio 1. Ensure you have properly [set up the extension](https://gitlab.com/gitlab-org/editor-extensions/gitlab-visual-studio-extension#setup). -1. From the **Tools > Options** menu, find the **GitLab** option. Ensure **Log Level** is set to **Debug**. -1. In **View > Output**, open the extension log. Change the dropdown list to **GitLab Extension** as the log filter. +1. From the **Tools** > **Options** menu, find the **GitLab** option. Ensure **Log Level** is set to **Debug**. +1. In **View** > **Output**, open the extension log. Change the dropdown list to **GitLab Extension** as the log filter. 1. Verify that the debug log contains similar output: ```shell diff --git a/doc/user/project/repository/commits/_index.md b/doc/user/project/repository/commits/_index.md index ad44199d52f5e6..9b78e32bef7702 100644 --- a/doc/user/project/repository/commits/_index.md +++ b/doc/user/project/repository/commits/_index.md @@ -34,7 +34,7 @@ The list shows: To view your repository's commit history: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. To view a commit's summary, select the **Toggle commit description** icon ({{< icon name="ellipsis_h">}}). This summary does not display file changes or statistics. @@ -46,7 +46,7 @@ Examine the specific changes made in any commit, including file modifications, a To view a commit's details: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. Select the commit to open the commit's details page. The commit's details page shows: @@ -65,7 +65,7 @@ To view all repository files and folders at a specific Git revision, such as a c branch name, or tag: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. Choose one of the following options: - Filter by Git revision: 1. At the top, select to open the **Select Git revision** dropdown list. @@ -84,7 +84,7 @@ Filter and search the commit history to find specific changes or track work by p To filter commits by a specific author: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. In the **Author** dropdown list, select or search for the author's name or username. If author filtering doesn't work for names with special characters, use the URL parameter format. @@ -95,7 +95,7 @@ For example, append `?author=Elliot%20Stevens` to the URL. To filter commits by Git revision, such as branch, tag, or commit SHA: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. In the dropdown list, select or search for a Git revision. For example, branch name, tag, or commit SHA. 1. Select the Git revision to view the list of filtered commits. @@ -105,7 +105,7 @@ To filter commits by Git revision, such as branch, tag, or commit SHA: To search for commits by message content: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. In the **Search by message** field, enter your search terms. You can also search by commit SHA, full or partial, to find a specific commit directly. @@ -122,7 +122,7 @@ Prerequisites: To cherry-pick a commit: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. Select the commit you want to cherry-pick. 1. In the upper-right corner, select **Options** and then **Cherry-pick**. 1. In the dialog: @@ -145,7 +145,7 @@ Prerequisites: To revert a commit: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. Select the commit you want to revert. 1. In the upper-right corner, select **Options** and then **Revert**. 1. In the dialog: @@ -162,7 +162,7 @@ GitLab prompts you to [create a new merge request](../../merge_requests/_index.m To download a commit's diff contents: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. Select the commit you want to download. 1. In the upper-right corner, select **Options**. 1. Under **Downloads**, select **Plain Diff**. @@ -179,7 +179,7 @@ For more information, see [signed commits](../signed_commits/_index.md). To view signature information: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. Find a commit with a **Verified** or **Unverified** badge. 1. Select the badge to view signature details including: - Signature type (GPG, SSH, or X.509) @@ -192,7 +192,7 @@ To view signature information: The commit list includes a CI/CD pipeline status icon next to each commit. To view the pipeline details: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. Select the pipeline status icon next to any commit. ## Related topics diff --git a/doc/user/project/repository/files/_index.md b/doc/user/project/repository/files/_index.md index e26f3466d62695..1b7951451587ef 100644 --- a/doc/user/project/repository/files/_index.md +++ b/doc/user/project/repository/files/_index.md @@ -153,7 +153,7 @@ The file finder uses fuzzy search and highlights results as you type. To search for a file, press t anywhere in your project, or: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Repository**. +1. Select **Code** > **Repository**. 1. In the upper right, select **Find file**. 1. On the dialog, start entering the filename: diff --git a/doc/user/project/repository/files/git_blame.md b/doc/user/project/repository/files/git_blame.md index 7b750b891c1cab..7713d25f0d7c5b 100644 --- a/doc/user/project/repository/files/git_blame.md +++ b/doc/user/project/repository/files/git_blame.md @@ -33,7 +33,7 @@ Prerequisites: To view the blame for a file: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Repository**. +1. Select **Code** > **Repository**. 1. Select the file you want to review. 1. Either: - To change the view of the current file, in the file header, select **Blame**. @@ -54,7 +54,7 @@ changes to light gray. To see earlier revisions of a specific line: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Repository**. +1. Select **Code** > **Repository**. 1. Select the file you want to review. 1. In the upper-right corner, select **Blame**, and go to the line you want to see. 1. Select **View blame prior to this change** ({{< icon name="doc-versions" >}}) diff --git a/doc/user/project/repository/files/git_history.md b/doc/user/project/repository/files/git_history.md index 8cacb48e8f6aea..14641ea52ae414 100644 --- a/doc/user/project/repository/files/git_history.md +++ b/doc/user/project/repository/files/git_history.md @@ -41,7 +41,7 @@ of the contributor when the user creates a commit. To see a file's Git history in the UI: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Repository**. +1. Select **Code** > **Repository**. 1. Go to your desired file in the repository. 1. In the last commit block, select **History**. diff --git a/doc/user/project/repository/forking_workflow.md b/doc/user/project/repository/forking_workflow.md index e10b966d1cc655..c1666a09288cf7 100644 --- a/doc/user/project/repository/forking_workflow.md +++ b/doc/user/project/repository/forking_workflow.md @@ -185,7 +185,7 @@ To restore the fork relationship, [use the API](../../../api/project_forks.md#cr To remove a fork relationship: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Advanced**. 1. In the **Remove fork relationship** section, select **Remove fork relationship**. 1. To confirm, enter the project path and select **Confirm**. diff --git a/doc/user/project/repository/push_rules.md b/doc/user/project/repository/push_rules.md index 5dc36ac31f572c..b3b021842bec9f 100644 --- a/doc/user/project/repository/push_rules.md +++ b/doc/user/project/repository/push_rules.md @@ -64,7 +64,7 @@ To override global push rules for a specific project, or to update the rules for an existing project to match new global push rules: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Push rules**. 1. Set the rule you want. 1. Select **Save push rules**. @@ -323,7 +323,7 @@ When you enable this rule: To enable the **Reject unsigned commits** push rule: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Push rules**. 1. Select **Reject unsigned commits**. 1. Select **Save push rules**. diff --git a/doc/user/project/repository/repository_size.md b/doc/user/project/repository/repository_size.md index f9f43023eb8003..301e4e3b7da78a 100644 --- a/doc/user/project/repository/repository_size.md +++ b/doc/user/project/repository/repository_size.md @@ -101,7 +101,7 @@ to produce a list of objects in a`commit-map` file. To clean up a repository: 1. On the left sidebar, select **Search or go to** and find your project. -1. Go to **Settings > Repository**. +1. Go to **Settings** > **Repository**. 1. Expand **Repository maintenance**. 1. Upload the list of objects to remove. For example, the `commit-map` file in the `filter-repo` directory. @@ -167,14 +167,14 @@ process. New commits pushed during blob removal can cause the operation to fail. To remove blobs from your repository: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Repository**. +1. Select **Settings** > **Repository**. 1. Expand **Repository maintenance**. 1. Select **Remove blobs**. 1. Enter a list of blob IDs to remove, each ID on its own line. 1. Select **Remove blobs**. 1. On the confirmation dialog, enter your project path. 1. Select **Yes, remove blobs**. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, select **Settings** > **General**. 1. Expand the section labeled **Advanced**. 1. Select **Run housekeeping**. Wait at least 30 minutes for the operation to complete. 1. In the same **Settings > General > Advanced** section, select **Prune unreachable objects**. diff --git a/doc/user/project/repository/signed_commits/_index.md b/doc/user/project/repository/signed_commits/_index.md index 884c611823de47..f7101f986f0e22 100644 --- a/doc/user/project/repository/signed_commits/_index.md +++ b/doc/user/project/repository/signed_commits/_index.md @@ -46,9 +46,9 @@ To review commits for a merge request, or for an entire project, and verify they 1. On the left sidebar, select **Search or go to** and find your project. 1. To review commits: - - For a project, select **Code > Commits**. + - For a project, select **Code** > **Commits**. - For a merge request: - 1. Select **Code > Merge requests**, then select your merge request. + 1. Select **Code** > **Merge requests**, then select your merge request. 1. Select **Commits**. 1. Identify the commit you want to review. Depending on the verification status of the signature, signed commits display either a **Verified** or **Unverified** badge. diff --git a/doc/user/project/repository/tags/_index.md b/doc/user/project/repository/tags/_index.md index 0bbea26172887c..768689ae506687 100644 --- a/doc/user/project/repository/tags/_index.md +++ b/doc/user/project/repository/tags/_index.md @@ -52,12 +52,12 @@ In the GitLab UI, each tag displays: To view all existing tags for a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Tags**. +1. Select **Code** > **Tags**. ## View tagged commits in the commits list 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Commits**. +1. Select **Code** > **Commits**. 1. Commits with a tag are labeled with a tag icon ({{< icon name="tag" >}}) and the name of the tag. This example shows a commit tagged `v1.26.0`: @@ -94,7 +94,7 @@ To create either a lightweight or annotated tag from the command line, and push To create a tag from the GitLab UI: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Tags**. +1. Select **Code** > **Tags**. 1. Select **New tag**. 1. Provide a **Tag name**. 1. For **Create from**, select an existing branch name, tag, or commit SHA. diff --git a/doc/user/project/repository/web_editor.md b/doc/user/project/repository/web_editor.md index 1a714033d3fd84..174defe7eb1eee 100644 --- a/doc/user/project/repository/web_editor.md +++ b/doc/user/project/repository/web_editor.md @@ -89,7 +89,7 @@ To edit a text file in the Web Editor: 1. On the left sidebar, select **Search or go to** and find your project. 1. Go to the file you want to edit. -1. Select **Edit > Edit single file**. +1. Select **Edit** > **Edit single file**. 1. Make your changes. 1. Select **Commit changes**. 1. In the **Commit message** field, enter a reason for the commit. @@ -126,7 +126,7 @@ To preview a Markdown file in the Web Editor: 1. On the left sidebar, select **Search or go to** and find your project. 1. Go to the file you want to preview. -1. Select **Edit > Edit single file**. +1. Select **Edit** > **Edit single file**. 1. Select the **Preview** tab. You can see a live Markdown preview alongside your content. @@ -155,7 +155,7 @@ you can edit a file and commit changes. To do this: 1. Go to the merge request. 1. Go to the file you want to edit. -1. Select **Edit > Edit single file**. +1. Select **Edit** > **Edit single file**. 1. Select **Commit changes**. 1. In **Commit message**, enter a reason for the commit. The following information is provided: `Your changes can be committed to because a merge request is open.` diff --git a/doc/user/project/settings/_index.md b/doc/user/project/settings/_index.md index 076fd9a4f2af7d..dc70fbcc21f837 100644 --- a/doc/user/project/settings/_index.md +++ b/doc/user/project/settings/_index.md @@ -17,7 +17,7 @@ title: Project settings To configure features and permissions for a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. To allow users to request access to the project, select the **Users can request access** checkbox. 1. To turn features on or off in the project, use the feature toggles. @@ -57,7 +57,7 @@ and accessible to project members, regardless of their role. To toggle the availability of individual features in a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. To change the availability of a feature, turn the toggle on or off. 1. Select **Save changes**. @@ -74,7 +74,7 @@ By default, project analytics are displayed under the **Analyze** item in the le To turn this feature off and remove the **Analyze** item from the left sidebar: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. Turn off the **Analytics** toggle. 1. Select **Save changes**. @@ -99,7 +99,7 @@ In some environments, users can submit a [CVE identifier request](../../applicat To turn off the CVE identifier request option in issues in your project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. Under **Issues**, turn off the **CVE ID requests in the issue sidebar** toggle. 1. Select **Save changes**. @@ -111,7 +111,7 @@ Prerequisites: - You must have the Owner role for the project. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Visibility, project features, permissions** section. 1. Clear the **Enable email notifications** checkbox. @@ -137,7 +137,7 @@ Prerequisites: To turn off diff previews for a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Visibility, project features, permissions** section. 1. Clear **Include diff previews**. 1. Select **Save changes**. @@ -168,7 +168,7 @@ In merge requests, you can change the default behavior so that the To set this default: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Merge requests**. +1. Select **Settings** > **Merge requests**. 1. Select **Enable "Delete source branch" option by default**. 1. Select **Save changes**. @@ -193,7 +193,7 @@ GitLab sends multiple [expiry emails](project_access_tokens.md#project-access-to To enable additional triggers for these webhooks: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand the **Visibility, project features, permissions** section. 1. Select the **Extended Group Access Tokens Expiry Webhook execution** checkbox. 1. Select **Save changes**. diff --git a/doc/user/project/settings/import_export.md b/doc/user/project/settings/import_export.md index 2f22cfc392539f..bdab62263a2d84 100644 --- a/doc/user/project/settings/import_export.md +++ b/doc/user/project/settings/import_export.md @@ -140,7 +140,7 @@ Before you can migrate projects on GitLab Self-Managed using file exports, GitLa To enable file exports as an import source for the destination instance: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Import and export settings**. 1. Scroll to **Import sources**. 1. Select the **GitLab export** checkbox. @@ -168,7 +168,7 @@ Prerequisites: To export a project and its data, follow these steps: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Advanced**. 1. Select **Export project**. 1. After the export is generated, you can: @@ -458,7 +458,7 @@ Prerequisites: To export the contents of a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. In the **Advanced** section, select **Export group**. 1. After the export is generated, you can: - Follow a link contained in an email that you should receive. diff --git a/doc/user/project/settings/project_access_tokens.md b/doc/user/project/settings/project_access_tokens.md index af65c42859bbc1..2c47a7a85efa86 100644 --- a/doc/user/project/settings/project_access_tokens.md +++ b/doc/user/project/settings/project_access_tokens.md @@ -84,7 +84,7 @@ The ability to create project access tokens without an expiry date was [deprecat To create a project access token: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Access tokens**. +1. Select **Settings** > **Access tokens**. 1. Select **Add new token**. 1. In **Token name**, enter a name. The token name is visible to any user with permissions to view the project. 1. Optional. In **Token description**, enter a description for the token. @@ -126,7 +126,7 @@ Tokens that belong to [an active token family](../../../api/personal_access_toke To revoke or rotate a project access token: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > Access tokens**. +1. Select **Settings** > **Access tokens**. 1. For the relevant token, select **Revoke** ({{< icon name="remove" >}}) or **Rotate** ({{< icon name="retry" >}}). 1. On the confirmation dialog, select **Revoke** or **Rotate**. @@ -168,7 +168,7 @@ To limit potential abuse, you can restrict users from creating tokens for a grou 1. On the left sidebar, select **Search or go to** and find your group. This group must be at the top level. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Permissions and group features**. 1. In **Permissions**, clear the **Users can create project access tokens and group access tokens in this group** checkbox. diff --git a/doc/user/project/system_notes.md b/doc/user/project/system_notes.md index 277987a352b600..3e60c1d5c5399d 100644 --- a/doc/user/project/system_notes.md +++ b/doc/user/project/system_notes.md @@ -42,7 +42,7 @@ Merge requests provide more granular filtering options. ### On an epic 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Epics**. +1. Select **Plan** > **Epics**. 1. Identify your desired epic, and select its title. 1. Go to the **Activity** section. 1. For **Sort or filter**, select **Show all activity**. @@ -50,14 +50,14 @@ Merge requests provide more granular filtering options. ### On an issue 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues** and find your issue. +1. Select **Plan** > **Issues** and find your issue. 1. Go to **Activity**. 1. For **Sort or filter**, select **Show all activity**. ### On a merge request 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Merge requests** and find your merge request. +1. Select **Code** > **Merge requests** and find your merge request. 1. Go to **Activity**. 1. For **Sort or filter**, select **Show all activity** to see all system notes. To narrow the types of system notes returned, select one or more of: diff --git a/doc/user/project/time_tracking.md b/doc/user/project/time_tracking.md index 6781a550d88c7f..d46126acda39b2 100644 --- a/doc/user/project/time_tracking.md +++ b/doc/user/project/time_tracking.md @@ -261,7 +261,7 @@ On GitLab Self-Managed, you can limit the display of time units to hours. To do so: 1. On the left sidebar, select **Search or go to**. -1. Select **Settings > Preferences**. +1. Select **Settings** > **Preferences**. 1. Expand **Localization**. 1. Under **Time tracking**, select the **Limit display of time tracking units to hours** checkbox. 1. Select **Save changes**. diff --git a/doc/user/project/working_with_projects.md b/doc/user/project/working_with_projects.md index 94cbf16b71a89e..913039bb824039 100644 --- a/doc/user/project/working_with_projects.md +++ b/doc/user/project/working_with_projects.md @@ -179,7 +179,7 @@ Prerequisites: - You must have at least the Maintainer role for the project. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. In the **Project name** text box, enter your project name. See the [limitations on project names](../reserved_names.md). 1. Optional. In the **Project description** text box, enter your project description. The description is limited to 2,000 characters. Components published in the CI/CD catalog require a project description. @@ -226,7 +226,7 @@ Prerequisites: To upload an avatar in your project settings: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. In the **Project avatar** section, select **Choose file**. 1. Select your avatar file. 1. Select **Save changes**. @@ -304,7 +304,7 @@ Prerequisites: To transfer a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Advanced**. 1. Under **Transfer project**, choose the namespace to transfer the project to. 1. Select **Transfer project**. @@ -350,7 +350,7 @@ Prerequisites: To delete a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Advanced**. 1. In the **Delete project** section, select **Delete project**. 1. On the confirmation dialog, enter the project name and select **Yes, delete project**. @@ -403,7 +403,7 @@ Prerequisites: To restore a project pending deletion: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Advanced**. 1. In the **Restore project** section, select **Restore project**. @@ -452,7 +452,7 @@ Prerequisites: To archive a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Advanced**. 1. In the **Archive project** section, select **Archive project**. 1. To confirm, select **OK**. @@ -473,7 +473,7 @@ Prerequisites: 1. In the **Sort projects** dropdown list, select **Show archived projects**. 1. In the **Filter by name** field, enter the project name. 1. Select the project link. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, select **Settings** > **General**. 1. Under **Advanced**, select **Expand**. 1. In the **Unarchive project** section, select **Unarchive project**. 1. To confirm, select **OK**. @@ -487,7 +487,7 @@ When a project is unarchived, its pull mirroring process will automatically resu To view the activity of a project: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Manage > Activity**. +1. Select **Manage** > **Activity**. 1. Optional. To filter activity by contribution type, select a tab: - **All**: All contributions by project members. @@ -569,7 +569,7 @@ For more information on redirect duration and its side-effects, see To rename a repository: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Advanced**. 1. In the **Change path** text box, edit the path. 1. Select **Change path**. diff --git a/doc/user/public_access.md b/doc/user/public_access.md index 641b25e5332477..f6d4f95e05304e 100644 --- a/doc/user/public_access.md +++ b/doc/user/public_access.md @@ -87,7 +87,7 @@ Prerequisites: - You must have the Owner role for a project. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. From the **Project visibility** dropdown list, select an option. The visibility setting for a project must be at least as restrictive @@ -103,7 +103,7 @@ Prerequisites: - You must have at least the Maintainer role for the project. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Visibility, project features, permissions**. 1. To enable or disable a feature, turn on or turn off the feature toggle. 1. Select **Save changes**. @@ -120,7 +120,7 @@ Prerequisites: to private if a project or subgroup in that group is public. 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > General**. +1. Select **Settings** > **General**. 1. Expand **Naming, visibility**. 1. For **Visibility level**, select an option. The visibility setting for a project must be at least as restrictive diff --git a/doc/user/search/_index.md b/doc/user/search/_index.md index 80c7544e246159..d312ae2e45f00e 100644 --- a/doc/user/search/_index.md +++ b/doc/user/search/_index.md @@ -95,7 +95,7 @@ To restrict `/search` to authenticated users only, do one of the following: - Restrict access in the **Admin** area: 1. On the left sidebar, at the bottom, select **Admin**. - 1. Select **Settings > Search**. + 1. Select **Settings** > **Search**. 1. Expand **Advanced search**. 1. Clear the **Allow unauthenticated users to use search** checkbox. 1. Select **Save changes**. @@ -103,7 +103,7 @@ To restrict `/search` to authenticated users only, do one of the following: To restrict global search to authenticated users only: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Visibility and access controls** 1. Select the **Restrict global search to authenticated users only** checkbox. 1. Select **Save changes**. @@ -134,7 +134,7 @@ All global search scopes are enabled by default on GitLab Self-Managed instances To disable one or more global search scopes: 1. On the left sidebar, at the bottom, select **Admin**. -1. Select **Settings > Search**. +1. Select **Settings** > **Search**. 1. Expand **Visibility and access controls**. 1. Clear the checkboxes for the scopes you want to disable. 1. Select **Save changes**. diff --git a/doc/user/shortcuts.md b/doc/user/shortcuts.md index 2cfaa27408ead8..81711c0a86a41d 100644 --- a/doc/user/shortcuts.md +++ b/doc/user/shortcuts.md @@ -76,23 +76,23 @@ relatively quickly to work, and they take you to another page in the project. | Keyboard shortcut | Description | |-----------------------------|-------------| | g + o | Go to the **Project overview** page. | -| g + v | Go to the project **Activity** page (**Manage > Activity**). | -| g + r | Go to the project **Releases** page (**Deploy > Releases**). | -| g + f | Go to the [project files](#project-files) (**Code > Repository**). | -| t | Open the project file search dialog. (**Code > Repository**, select **Find Files**). | -| g + c | Go to the project **Commits** page (**Code > Commits**). | -| g + n | Go to the [**Repository graph**](#repository-graph) page (**Code > Repository graph**). | -| g + d | Go to the charts in the **Repository analytics** page (**Analyze > Repository analytics**). | -| g + i | Go to the project **Issues** page (**Plan > Issues**). | -| i | Go to the **New Issue** page (**Plan > Issues**, select **New issue** ). | -| g + b | Go to the project **Issue boards** page (**Plan > Issue boards**). | -| g + m | Go to the project [**Merge requests**](project/merge_requests/_index.md) page (**Code > Merge requests**). | -| g + p | Go to the CI/CD **Pipelines** page (**Build > Pipelines**). | -| g + j | Go to the CI/CD **Jobs** page (**Build > Jobs**). | -| g + e | Go to the project **Environments** page (**Operate > Environments**). | -| g + k | Go to the project **Kubernetes clusters** integration page (**Operate > Kubernetes clusters**). You must have at least [`maintainer` permissions](permissions.md) to access this page. | -| g + s | Go to the project **Snippets** page (**Code > Snippets**). | -| g + w | Go to the [project wiki](project/wiki/_index.md) (**Plan > Wiki**), if enabled. | +| g + v | Go to the project **Activity** page (**Manage** > **Activity**). | +| g + r | Go to the project **Releases** page (**Deploy** > **Releases**). | +| g + f | Go to the [project files](#project-files) (**Code** > **Repository**). | +| t | Open the project file search dialog. (**Code** > **Repository**, select **Find Files**). | +| g + c | Go to the project **Commits** page (**Code** > **Commits**). | +| g + n | Go to the [**Repository graph**](#repository-graph) page (**Code** > **Repository graph**). | +| g + d | Go to the charts in the **Repository analytics** page (**Analyze** > **Repository analytics**). | +| g + i | Go to the project **Issues** page (**Plan** > **Issues**). | +| i | Go to the **New Issue** page (**Plan** > **Issues**, select **New issue** ). | +| g + b | Go to the project **Issue boards** page (**Plan** > **Issue boards**). | +| g + m | Go to the project [**Merge requests**](project/merge_requests/_index.md) page (**Code** > **Merge requests**). | +| g + p | Go to the CI/CD **Pipelines** page (**Build** > **Pipelines**). | +| g + j | Go to the CI/CD **Jobs** page (**Build** > **Jobs**). | +| g + e | Go to the project **Environments** page (**Operate** > **Environments**). | +| g + k | Go to the project **Kubernetes clusters** integration page (**Operate** > **Kubernetes clusters**). You must have at least [`maintainer` permissions](permissions.md) to access this page. | +| g + s | Go to the project **Snippets** page (**Code** > **Snippets**). | +| g + w | Go to the [project wiki](project/wiki/_index.md) (**Plan** > **Wiki**), if enabled. | | . | Open the [Web IDE](project/web_ide/_index.md). | ### Issues @@ -135,21 +135,21 @@ These shortcuts are available when viewing [merge requests](project/merge_reques ### Project files These shortcuts are available when browsing the files in a project (go to -**Code > Repository**): +**Code** > **Repository**): | Keyboard shortcut | Description | |-------------------|-------------| -| ↑ | Move selection up (only while searching for files, **Code > Repository**, then select **Find File**). | -| ↓ | Move selection down (only while searching for files, **Code > Repository**, then select **Find File**). | -| Enter | Open selection (only while searching for files, **Code > Repository**, then select **Find File**). | -| Escape | Go back to the **Find File** screen (only while searching for files, **Code > Repository**, then select **Find File**). | +| ↑ | Move selection up (only while searching for files, **Code** > **Repository**, then select **Find File**). | +| ↓ | Move selection down (only while searching for files, **Code** > **Repository**, then select **Find File**). | +| Enter | Open selection (only while searching for files, **Code** > **Repository**, then select **Find File**). | +| Escape | Go back to the **Find File** screen (only while searching for files, **Code** > **Repository**, then select **Find File**). | | y | Go to file permalink (only while viewing a file). | | . | Open the [Web IDE](project/web_ide/_index.md). | ### Repository graph These shortcuts are available when viewing the project [repository graph](project/repository/_index.md#repository-history-graph) -page (go to **Code > Repository graph**): +page (go to **Code** > **Repository graph**): | Keyboard shortcut | Description | |--------------------------------------------------------------------|-------------| diff --git a/doc/user/snippets.md b/doc/user/snippets.md index c6393ea880f491..2949f7c54656a4 100644 --- a/doc/user/snippets.md +++ b/doc/user/snippets.md @@ -80,7 +80,7 @@ To discover all snippets visible to you in GitLab, you can: - View a project's snippets: 1. On the left sidebar, select **Search or go to** and find your project. - 1. Select **Code > Snippets**. + 1. Select **Code** > **Snippets**. - View all the snippets you created: 1. On the left sidebar, select **Search or go to**. 1. Select **Your work**. @@ -100,7 +100,7 @@ To discover all snippets visible to you in GitLab, you can: Project snippets are enabled and available by default. To change their default visibility: -1. In your project, go to **Settings > General**. +1. In your project, go to **Settings** > **General**. 1. Expand the **Visibility, project features, permissions** section, and scroll to **Snippets**. 1. Toggle the default visibility, and select whether snippets can be viewed by everyone, or only project members. @@ -193,7 +193,7 @@ To embed a snippet: 1. Confirm your snippet is publicly visible: - If it's a project snippet, the project must be public. - The snippet is publicly visible. - - In your project, go to **Settings > General**. Expand the **Visibility, project features, permissions** + - In your project, go to **Settings** > **General**. Expand the **Visibility, project features, permissions** section, and scroll to **Snippets**. Set the snippet permission to **Everyone with access**. 1. In your snippet's **Embed** section, select **Copy** to copy a one-line script you can add to any website or blog post. For example: @@ -246,7 +246,7 @@ Prerequisites: To do this task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Code > Snippets**. +1. Select **Code** > **Snippets**. 1. Select the snippet you want to report as spam. 1. Select **Submit as spam**. diff --git a/doc/user/storage_usage_quotas.md b/doc/user/storage_usage_quotas.md index 2384898230e21f..7ab91285079eac 100644 --- a/doc/user/storage_usage_quotas.md +++ b/doc/user/storage_usage_quotas.md @@ -51,7 +51,7 @@ Prerequisites: To view storage: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Settings > Usage Quotas**. +1. Select **Settings** > **Usage Quotas**. 1. Select the **Storage** tab to see namespace storage usage. 1. To view storage usage for a project, in the table at the bottom, select a project. Storage usage is updated every 90 minutes. @@ -70,7 +70,7 @@ A cost factor is applied to the storage consumed by project forks so that forks To view the amount of namespace storage the fork has used: 1. On the left sidebar, select **Search or go to** and find your project or group. -1. Select **Settings > Usage Quotas**. +1. Select **Settings** > **Usage Quotas**. 1. Select the **Storage** tab. The **Total** column displays the amount of namespace storage used by the fork as a portion of the actual size of the fork on disk. The cost factor applies to the project repository, LFS objects, job artifacts, packages, snippets, and the wiki. diff --git a/doc/user/tasks.md b/doc/user/tasks.md index ad7deeef7a3934..0a486c376699d6 100644 --- a/doc/user/tasks.md +++ b/doc/user/tasks.md @@ -72,7 +72,7 @@ Prerequisites: To create a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select **Add**. 1. Select **New task**. 1. Enter the task title. @@ -92,7 +92,7 @@ Prerequisites: - You must have at least the Guest role for the project. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, hover over a task list item and select the options menu ({{< icon name="ellipsis_v" >}}). 1. Select **Convert to task**. @@ -114,7 +114,7 @@ Prerequisites: To add a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select **Add**. 1. Select **Existing task**. 1. Search tasks by title. @@ -136,7 +136,7 @@ Prerequisites: To edit a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the task you want to edit. The task window opens. 1. Optional. To edit the title, select it and make your changes. @@ -164,7 +164,7 @@ Prerequisites: To edit the description of a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the title of the task you want to edit. The task window opens. 1. Next to **Description**, select the edit icon ({{< icon name="pencil" >}}). The description text box appears. @@ -187,7 +187,7 @@ Prerequisites: To promote a task to an issue: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the task you want to edit. The task window opens. 1. Unlink the parent issue and promote the task: In the task window, use these two @@ -232,7 +232,7 @@ Prerequisites: To convert a task into another item type: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**. +1. Select **Plan** > **Issues**. 1. In the issue list, find your task. 1. Optional. If the task has a parent issue assigned, remove it. Add a comment to the task with the `/remove_parent` quick action. @@ -261,7 +261,7 @@ It's not possible to connect them again. To remove a task from an issue: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the options menu ({{< icon name="ellipsis_v" >}}) next to the task you want to remove. 1. Select **Remove task**. @@ -283,7 +283,7 @@ Prerequisites: To delete a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the task you want to edit. 1. In the task window, in the options menu ({{< icon name="ellipsis_v" >}}), select **Delete task**. 1. Select **OK**. @@ -341,7 +341,7 @@ Prerequisites: To change the status of a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your task to view it. +1. Select **Plan** > **Issues**, then select your task to view it. 1. On the right sidebar, in the **Status** section, select **Edit**. 1. From the dropdown list, select the status. @@ -370,7 +370,7 @@ Prerequisites: To change the assignee on a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the title of the task you want to edit. The task window opens. 1. Next to **Assignees**, select **Add assignees**. @@ -393,7 +393,7 @@ Prerequisites: To add [labels](project/labels.md) to a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the title of the task you want to edit. The task window opens. 1. Next to **Labels**, select **Add labels**. 1. From the dropdown list, select the labels to add. @@ -420,7 +420,7 @@ You can set start and due dates on a task to show when work should begin and end To set a due date: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the title of the task you want to edit. The task window opens. 1. If the task already has a due date next to **Due date**, select it. Otherwise, select **Add due date**. @@ -459,7 +459,7 @@ Prerequisites: To add a task to a milestone: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the title of the task you want to edit. The task window opens. 1. Next to **Milestone**, select **Add to milestone**. @@ -492,7 +492,7 @@ This value is visible only when you view a task. To set issue weight of a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the title of the task you want to edit. The task window opens. 1. Next to **Weight**, select **Edit**. @@ -525,7 +525,7 @@ Prerequisites: To add a task to an iteration: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the title of the task you want to edit. The task window opens. 1. Next to **Iteration**, select **Add to iteration**. @@ -616,7 +616,7 @@ To refer to a task elsewhere in GitLab, you can use its full URL or a short refe To copy the task reference to your clipboard: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select your task. 1. In the upper-right corner, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}), then select **Copy Reference**. @@ -641,7 +641,7 @@ For more information about creating comments by sending an email and the necessa To copy the task's email address: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the upper-right corner, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}), then select **Copy task email address**. ## Set an issue as a parent @@ -660,7 +660,7 @@ Prerequisites: To set an issue as a parent of a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select the title of the task you want to edit. The task window opens. 1. Next to **Parent**, from the dropdown list, select the parent to add. @@ -838,7 +838,7 @@ Prerequisites: To link an item to a task: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select your task. 1. In the **Linked items** section of a task, select **Add**. @@ -861,7 +861,7 @@ Prerequisites: - You must have at least the Guest role for the project. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Plan > Issues**, then select your issue to view it. +1. Select **Plan** > **Issues**, then select your issue to view it. 1. In the issue description, in the **Child items** section, select your task. 1. In the **Linked items** section of a task, next to each item, select the vertical ellipsis ({{< icon name="ellipsis_v" >}}) and then select **Remove**. diff --git a/doc/user/version.md b/doc/user/version.md index 72bd4b263a6525..15f84b8c7e4020 100644 --- a/doc/user/version.md +++ b/doc/user/version.md @@ -23,7 +23,7 @@ Prerequisites: To find the version of GitLab: -- On the left sidebar, at the bottom, select **Help > Help**. +- On the left sidebar, at the bottom, select **Help** > **Help**. The version is displayed at the top of the page. diff --git a/doc/user/workspace/_index.md b/doc/user/workspace/_index.md index 751293b34fbcec..c8c3c88a72c8ed 100644 --- a/doc/user/workspace/_index.md +++ b/doc/user/workspace/_index.md @@ -97,7 +97,7 @@ To clean up orphaned resources, an administrator must manually delete the worksp To manage all workspaces associated with an agent: 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Kubernetes clusters**. +1. Select **Operate** > **Kubernetes clusters**. 1. Select the agent configured for remote development. 1. Select the **Workspaces** tab. 1. From the list, you can restart, stop, or terminate an existing workspace. diff --git a/doc/user/workspace/configuration.md b/doc/user/workspace/configuration.md index 4adbe5c93453c7..7a4be3f17521fb 100644 --- a/doc/user/workspace/configuration.md +++ b/doc/user/workspace/configuration.md @@ -73,7 +73,7 @@ Prerequisites: {{< tab title="From a project" >}} 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Edit > New workspace**. +1. Select **Edit** > **New workspace**. 1. From the **Cluster agent** dropdown list, select a cluster agent owned by the group the project belongs to. 1. From the **Git reference** dropdown list, select the branch, tag, or commit hash GitLab uses to create the workspace. By default, this is the branch you're viewing. @@ -89,9 +89,9 @@ Prerequisites: {{< tab title="From a merge request" >}} 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Code > Merge requests**. +1. On the left sidebar, select **Code** > **Merge requests**. 1. Select the merge request you want to create a workspace for. -1. Select **Code > Open in Workspace**. +1. Select **Code** > **Open in Workspace**. 1. From the **Cluster agent** dropdown list, select a cluster agent owned by the group the project belongs to. 1. From the **Git reference** dropdown list, select the branch, tag, or commit hash GitLab uses to create the workspace. By default, this is the source branch of the merge request. diff --git a/doc/user/workspace/gitlab_agent_configuration.md b/doc/user/workspace/gitlab_agent_configuration.md index 01d1e072993a24..4cd27c08d3cee8 100644 --- a/doc/user/workspace/gitlab_agent_configuration.md +++ b/doc/user/workspace/gitlab_agent_configuration.md @@ -86,7 +86,7 @@ Prerequisites: To allow a cluster agent for workspaces in a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. On the left sidebar, select **Settings > Workspaces**. +1. On the left sidebar, select **Settings** > **Workspaces**. 1. In the **Group agents** section, select the **All agents** tab. 1. From the list of available agents, find the agent with status **Blocked**, and select **Allow**. 1. On the confirmation dialog, select **Allow agent**. @@ -103,7 +103,7 @@ Prerequisites: To remove an allowed cluster agent from a group: 1. On the left sidebar, select **Search or go to** and find your group. -1. On the left sidebar, select **Settings > Workspaces**. +1. On the left sidebar, select **Settings** > **Workspaces**. 1. In the **Group agents** section, select the **Allowed agents** tab. 1. From the list of allowed agents, find the agent you want to remove, and select **Block**. 1. On the confirmation dialog, select **Block agent**. @@ -134,7 +134,7 @@ Prerequisites: To allow a cluster agent for workspaces on the instance: 1. On the left sidebar, at the bottom, select **Admin**. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, select **Settings** > **General**. 1. Expand **Available agents for workspaces**. 1. From the list of agents with workspaces enabled, find the agent you want to allow, and select the availability toggle. @@ -154,7 +154,7 @@ Prerequisites: To remove an allowed cluster agent from the instance: 1. On the left sidebar, at the bottom, select **Admin**. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, select **Settings** > **General**. 1. Expand **Available agents for workspaces**. 1. From the list of allowed agents, find the agent you want to remove, and clear the availability toggle. diff --git a/doc/user/workspace/set_up_gitlab_agent_and_proxies.md b/doc/user/workspace/set_up_gitlab_agent_and_proxies.md index 7b464a2f50f2fb..3b276bba528419 100644 --- a/doc/user/workspace/set_up_gitlab_agent_and_proxies.md +++ b/doc/user/workspace/set_up_gitlab_agent_and_proxies.md @@ -135,7 +135,7 @@ Only one agent is required. You can create workspaces from all projects in a gro To allow your GitLab agent for Kubernetes in a group and make it available to all projects in that group: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > Workspaces**. +1. Select **Settings** > **Workspaces**. 1. In the **Group agents** section, select the **All agents** tab. 1. For the GitLab agent for Kubernetes, select **Allow**. 1. On the confirmation dialog, select **Allow agent**. diff --git a/doc/user/workspace/set_up_infrastructure.md b/doc/user/workspace/set_up_infrastructure.md index 5b215e0d759af2..babeae1857dcfe 100644 --- a/doc/user/workspace/set_up_infrastructure.md +++ b/doc/user/workspace/set_up_infrastructure.md @@ -156,7 +156,7 @@ To create a token for the agent: 1. Go to your group. 1. On the left sidebar, select **Search or go to** and find your project. -1. Select **Operate > Kubernetes clusters**. +1. Select **Operate** > **Kubernetes clusters**. 1. Select **Connect a cluster**. 1. Enter a name for your agent and save for later use. For example, `gitlab-workspaces-agentk-eks`. 1. Select **Create and register**. @@ -271,7 +271,7 @@ resources in AWS. To run the pipeline: 1. Create a new pipeline in your GitLab project: - 1. On the left sidebar, select **Build > Pipelines**. + 1. On the left sidebar, select **Build** > **Pipelines**. 1. Select **New pipeline** and select **New pipeline** again to confirm. 1. Verify the `plan` job succeeds, then manually trigger the `apply` job. @@ -309,7 +309,7 @@ Next, you'll authorize the GitLab agent for Kubernetes to connect to your GitLab To authorize the agent: 1. On the left sidebar, select **Search or go to** and find your group. -1. Select **Settings > Workspaces**. +1. Select **Settings** > **Workspaces**. 1. In the **Group agents** section, select the **All agents** tab. 1. From the list of available agents, find the agent with status **Blocked**, and select **Allow**. 1. On the confirmation dialog, select **Allow agent**. diff --git a/doc/user/workspace/workspaces_troubleshooting.md b/doc/user/workspace/workspaces_troubleshooting.md index 83474aab247787..914931d8999891 100644 --- a/doc/user/workspace/workspaces_troubleshooting.md +++ b/doc/user/workspace/workspaces_troubleshooting.md @@ -64,7 +64,7 @@ If the names are different, rename the folder to match the agent name exactly. Verify the agent is connected to GitLab: 1. Go to your group. -1. Select **Operate** > **Kubernetes clusters**. +1. Select **Operate**** > ****Kubernetes clusters**. 1. Verify if **Connection status** is **Connected**. If not connected, check the agent logs: ```shell -- GitLab From 291f0f0474bdc86c916ef6288a63a5b1c0975417 Mon Sep 17 00:00:00 2001 From: Suzanne Selhorn Date: Mon, 14 Jul 2025 09:02:17 -0700 Subject: [PATCH 3/3] Removed script file --- foo.py | 250 --------------------------------------------------------- 1 file changed, 250 deletions(-) delete mode 100644 foo.py diff --git a/foo.py b/foo.py deleted file mode 100644 index b88fe3edac7c62..00000000000000 --- a/foo.py +++ /dev/null @@ -1,250 +0,0 @@ -#!/usr/bin/env python3 -""" -GitLab Markdown Bold Formatter -Fixes bold formatting around the '>' character in GitLab documentation. -Moves '>' outside of bold formatting to comply with style guidelines. -""" - -import os -import re -import glob -from pathlib import Path -from typing import List, Tuple, Dict - -def find_markdown_files(root_dir: str) -> List[str]: - """Find all markdown files in the directory and subdirectories.""" - pattern = os.path.join(root_dir, '**', '*.md') - return glob.glob(pattern, recursive=True) - -def should_skip_line(line: str) -> bool: - """ - Check if a line should be skipped from processing. - - Skip: - - Lines inside code blocks (```...```) - - Lines with alerts like {{< alert type="note" >}} - - Lines with tab titles like {{< tab title="Enterprise Edition" >}} - """ - # Check for alerts - if re.search(r'\{\{<\s*alert\s+.*>\}\}', line): - return True - - # Check for tab titles - if re.search(r'\{\{<\s*tab\s+title=.*>\}\}', line): - return True - - return False - -def fix_bold_formatting(content: str) -> Tuple[str, int]: - """ - Fix bold formatting around '>' character. - - Only fixes this pattern: - - **text > text** -> **text** > **text** - - Skips: - - Code blocks - - Alert shortcodes - - Tab title shortcodes - - Returns: (fixed_content, number_of_changes) - """ - changes = 0 - lines = content.split('\n') - in_code_block = False - processed_lines = [] - - for line in lines: - # Track code block state - if line.strip().startswith('```'): - in_code_block = not in_code_block - processed_lines.append(line) - continue - - # Skip processing if we're in a code block or this line should be skipped - if in_code_block or should_skip_line(line): - processed_lines.append(line) - continue - - # Process the line for bold formatting fixes - original_line = line - - # Only Pattern: **text > text** -> **text** > **text** - # This handles cases like **Overview > Users** but avoids HTML/markdown syntax - # More specific pattern that requires word characters and avoids HTML tags - pattern = r'\*\*([A-Za-z0-9\s]+?)\s*>\s*([A-Za-z0-9\s]+?)\*\*' - def replace_pattern(match): - nonlocal changes - # Additional check to avoid HTML/markdown syntax - left_part = match.group(1).strip() - right_part = match.group(2).strip() - - # Skip if it looks like HTML or contains special characters that suggest it's not UI navigation - if ('<' in left_part or '>' in left_part or - '<' in right_part or '>' in right_part or - left_part.endswith('br') or - '[' in left_part or ']' in left_part or - '[' in right_part or ']' in right_part): - return match.group(0) # Return original match unchanged - - changes += 1 - return f'**{left_part}** > **{right_part}**' - - line = re.sub(pattern, replace_pattern, line) - - processed_lines.append(line) - - return '\n'.join(processed_lines), changes - -def process_file(filepath: str) -> Dict[str, any]: - """Process a single markdown file.""" - try: - with open(filepath, 'r', encoding='utf-8') as f: - original_content = f.read() - - fixed_content, changes = fix_bold_formatting(original_content) - - if changes > 0: - # Write fixed content - with open(filepath, 'w', encoding='utf-8') as f: - f.write(fixed_content) - - return { - 'filepath': filepath, - 'changes': changes, - 'status': 'modified' - } - else: - return { - 'filepath': filepath, - 'changes': 0, - 'status': 'no_changes' - } - - except Exception as e: - return { - 'filepath': filepath, - 'changes': 0, - 'status': 'error', - 'error': str(e) - } - -def process_batch(files: List[str], batch_num: int) -> Dict[str, any]: - """Process a batch of files.""" - print(f"\nProcessing batch {batch_num} ({len(files)} files)...") - - results = { - 'batch_num': batch_num, - 'files_processed': 0, - 'files_modified': 0, - 'total_changes': 0, - 'errors': [], - 'modified_files': [] - } - - for filepath in files: - result = process_file(filepath) - results['files_processed'] += 1 - - if result['status'] == 'modified': - results['files_modified'] += 1 - results['total_changes'] += result['changes'] - results['modified_files'].append({ - 'file': result['filepath'], - 'changes': result['changes'] - }) - print(f" ✓ {result['filepath']} ({result['changes']} changes)") - - elif result['status'] == 'error': - results['errors'].append({ - 'file': result['filepath'], - 'error': result['error'] - }) - print(f" ✗ {result['filepath']} (ERROR: {result['error']})") - - else: - print(f" - {result['filepath']} (no changes needed)") - - return results - -def main(): - # Configuration - ROOT_DIR = "/Users/sselhorn/dev/gitlab/gitlab/doc" - BATCH_SIZE = 50 - - print("GitLab Markdown Bold Formatter") - print("=" * 40) - print(f"Root directory: {ROOT_DIR}") - print(f"Batch size: {BATCH_SIZE}") - - # Verify directory exists - if not os.path.exists(ROOT_DIR): - print(f"Error: Directory {ROOT_DIR} does not exist!") - return - - # Find all markdown files - print("\nFinding markdown files...") - markdown_files = find_markdown_files(ROOT_DIR) - - if not markdown_files: - print("No markdown files found!") - return - - print(f"Found {len(markdown_files)} markdown files") - - # Process confirmation - response = input(f"\nDo you want to process these files? (y/N): ") - if response.lower() != 'y': - print("Operation cancelled.") - return - - # Process files in batches - all_results = [] - total_files = len(markdown_files) - - for i in range(0, total_files, BATCH_SIZE): - batch = markdown_files[i:i + BATCH_SIZE] - batch_num = (i // BATCH_SIZE) + 1 - - result = process_batch(batch, batch_num) - all_results.append(result) - - # Show batch summary - print(f"Batch {batch_num} complete: {result['files_modified']}/{result['files_processed']} files modified, {result['total_changes']} total changes") - - # Ask to continue if there are more batches - if i + BATCH_SIZE < total_files: - response = input(f"\nContinue with next batch? (Y/n): ") - if response.lower() == 'n': - print("Processing stopped by user.") - break - - # Final summary - print("\n" + "=" * 40) - print("FINAL SUMMARY") - print("=" * 40) - - total_processed = sum(r['files_processed'] for r in all_results) - total_modified = sum(r['files_modified'] for r in all_results) - total_changes = sum(r['total_changes'] for r in all_results) - total_errors = sum(len(r['errors']) for r in all_results) - - print(f"Files processed: {total_processed}") - print(f"Files modified: {total_modified}") - print(f"Total changes: {total_changes}") - print(f"Errors: {total_errors}") - - if total_modified > 0: - print(f"\nModified files:") - for result in all_results: - for mod_file in result['modified_files']: - print(f" {mod_file['file']} ({mod_file['changes']} changes)") - - if total_errors > 0: - print(f"\nErrors occurred:") - for result in all_results: - for error in result['errors']: - print(f" {error['file']}: {error['error']}") - -if __name__ == "__main__": - main() \ No newline at end of file -- GitLab