diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-06-15 15:08:47 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-06-15 15:08:47 +0300 |
commit | 717436a767395d0ed850a16d07f19cd51c3d4551 (patch) | |
tree | 5c2d69721710081da88c8dcf097813e2f40c062c /doc | |
parent | 5a14a0fe63ac7dace9821be554ad3b3951529708 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc')
38 files changed, 378 insertions, 280 deletions
diff --git a/doc/administration/geo/replication/troubleshooting.md b/doc/administration/geo/replication/troubleshooting.md index f326a6940d5..4047167e4af 100644 --- a/doc/administration/geo/replication/troubleshooting.md +++ b/doc/administration/geo/replication/troubleshooting.md @@ -105,9 +105,7 @@ Checking Geo ... Finished You can also specify a custom NTP server using environment variables. For example: ```shell -export NTP_HOST="ntp.ubuntu.com" -export NTP_TIMEOUT="30" -sudo gitlab-rake gitlab:geo:check +sudo gitlab-rake gitlab:geo:check NTP_HOST="ntp.ubuntu.com" NTP_TIMEOUT="30" ``` The following environment variables are supported. diff --git a/doc/api/graphql/reference/index.md b/doc/api/graphql/reference/index.md index ebcad6aa12e..db39b1b59a4 100644 --- a/doc/api/graphql/reference/index.md +++ b/doc/api/graphql/reference/index.md @@ -12712,6 +12712,7 @@ Represents the total number of issues and their weights for a particular day. | <a id="cicatalogresourceforkscount"></a>`forksCount` **{warning-solid}** | [`Int!`](#int) | **Introduced** in 16.1. This feature is an Experiment. It can be changed or removed at any time. Number of times the catalog resource has been forked. | | <a id="cicatalogresourceicon"></a>`icon` **{warning-solid}** | [`String`](#string) | **Introduced** in 15.11. This feature is an Experiment. It can be changed or removed at any time. Icon for the catalog resource. | | <a id="cicatalogresourceid"></a>`id` **{warning-solid}** | [`ID!`](#id) | **Introduced** in 15.11. This feature is an Experiment. It can be changed or removed at any time. ID of the catalog resource. | +| <a id="cicatalogresourcelatestversion"></a>`latestVersion` **{warning-solid}** | [`Release`](#release) | **Introduced** in 16.1. This feature is an Experiment. It can be changed or removed at any time. Latest version of the catalog resource. | | <a id="cicatalogresourcename"></a>`name` **{warning-solid}** | [`String`](#string) | **Introduced** in 15.11. This feature is an Experiment. It can be changed or removed at any time. Name of the catalog resource. | | <a id="cicatalogresourcereadmehtml"></a>`readmeHtml` | [`String!`](#string) | GitLab Flavored Markdown rendering of `readme`. | | <a id="cicatalogresourcerootnamespace"></a>`rootNamespace` **{warning-solid}** | [`Namespace`](#namespace) | **Introduced** in 16.1. This feature is an Experiment. It can be changed or removed at any time. Root namespace of the catalog resource. | @@ -12725,8 +12726,9 @@ Represents the total number of issues and their weights for a particular day. Versions of the catalog resource. WARNING: -**Introduced** in 16.1. -This feature is an Experiment. It can be changed or removed at any time. +**Deprecated** in 16.1. +Causes performance degradation. +Use: `latest_version`. Returns [`ReleaseConnection`](#releaseconnection). diff --git a/doc/ci/examples/deployment/index.md b/doc/ci/examples/deployment/index.md index 664ce84c488..a156cf1acb0 100644 --- a/doc/ci/examples/deployment/index.md +++ b/doc/ci/examples/deployment/index.md @@ -121,8 +121,8 @@ We also use two secure variables: To store API keys as secure variables: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > CI/CD**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > CI/CD**. 1. Expand **Variables**. The variables defined in the project settings are sent along with the build script to the runner. diff --git a/doc/ci/examples/semantic-release.md b/doc/ci/examples/semantic-release.md index 2146d76e4d6..00260199179 100644 --- a/doc/ci/examples/semantic-release.md +++ b/doc/ci/examples/semantic-release.md @@ -90,14 +90,14 @@ As part of publishing a package, semantic-release increases the version number i <!-- markdownlint-disable MD044 --> -1. On the top bar, in the upper-right corner, select your avatar. -1. On the left sidebar, select **Access Tokens**. +1. On the left sidebar, select your avatar. +1. Select **Preferences > Access Tokens**. 1. In the **Token name** box, enter a token name. 1. Under **select scopes**, select the **api** checkbox. 1. Select **Create project access token**. 1. Copy the value. -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > CI/CD**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > CI/CD**. 1. Expand **Variables**. 1. Select **Add variable**. 1. In the **Key** box, enter `GITLAB_TOKEN`. diff --git a/doc/ci/jobs/ci_job_token.md b/doc/ci/jobs/ci_job_token.md index b24dbc8be45..a60aaa04ea1 100644 --- a/doc/ci/jobs/ci_job_token.md +++ b/doc/ci/jobs/ci_job_token.md @@ -117,8 +117,8 @@ Prerequisite: To disable the job token scope allowlist: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > CI/CD**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > CI/CD**. 1. Expand **Token Access**. 1. Toggle **Allow access to this project with a CI_JOB_TOKEN** to disabled. Enabled by default in new projects. @@ -138,8 +138,8 @@ Prerequisite: To add a project: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > CI/CD**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > CI/CD**. 1. Expand **Token Access**. 1. Verify **Allow access to this project with a CI_JOB_TOKEN** is enabled. 1. Under **Allow CI job tokens from the following projects to access this project**, @@ -180,8 +180,8 @@ Prerequisite: To configure the job token scope: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > CI/CD**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > CI/CD**. 1. Expand **Token Access**. 1. Toggle **Limit CI_JOB_TOKEN access** to enabled. 1. Optional. Add existing projects to the token's access scope. The user adding a diff --git a/doc/ci/jobs/index.md b/doc/ci/jobs/index.md index c446d89da41..a0c0fc43502 100644 --- a/doc/ci/jobs/index.md +++ b/doc/ci/jobs/index.md @@ -48,8 +48,8 @@ Selecting an individual job shows you its job log, and allows you to: To view the full list of jobs that ran in a project: -1. On the top bar, select **Main menu > Projects** and find the project. -1. On the left sidebar, select **CI/CD > Jobs**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Build > Jobs**. You can filter the list by [job status](#the-order-of-jobs-in-a-pipeline). diff --git a/doc/ci/jobs/job_artifacts.md b/doc/ci/jobs/job_artifacts.md index 6dbf14c9d43..95d939c7027 100644 --- a/doc/ci/jobs/job_artifacts.md +++ b/doc/ci/jobs/job_artifacts.md @@ -299,8 +299,8 @@ You can also delete individual artifacts from the [**Artifacts** page](#bulk-del You can delete multiple artifacts at the same time: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **CI/CD > Artifacts**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +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**. @@ -341,8 +341,8 @@ Keeping the latest artifacts can use a large amount of storage space in projects with a lot of jobs or large artifacts. If the latest artifacts are not needed in a project, you can disable this behavior to save space: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > CI/CD**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > CI/CD**. 1. Expand **Artifacts**. 1. Clear the **Keep artifacts from most recent successful jobs** checkbox. diff --git a/doc/ci/pipelines/cicd_minutes.md b/doc/ci/pipelines/cicd_minutes.md index 1dff0ada845..c29d23cfff7 100644 --- a/doc/ci/pipelines/cicd_minutes.md +++ b/doc/ci/pipelines/cicd_minutes.md @@ -54,7 +54,8 @@ Prerequisite: To change the default quota that applies to all namespaces: -1. On the top bar, select **Main menu > Admin**. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **Admin Area**. 1. On the left sidebar, select **Settings > CI/CD**. 1. Expand **Continuous Integration and Deployment**. 1. In the **Compute quota** box, enter a limit. @@ -75,7 +76,8 @@ Prerequisite: To set a compute quota for a namespace: -1. On the top bar, select **Main menu > Admin**. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **Admin Area**. 1. On the left sidebar, select **Overview > Groups**. 1. For the group you want to update, select **Edit**. 1. In the **Compute quota** box, enter the maximum number of units of compute. @@ -105,8 +107,9 @@ Prerequisite: To view compute usage for your group: -1. On the top bar, select **Main menu > Groups** and find your group. The group must not be a subgroup. -1. On the left sidebar, select **Settings > Usage Quotas**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to + find your group. The group must not be a subgroup. +1. Select **Settings > Usage Quotas**. 1. Select the **Pipelines** tab. The projects list shows projects with compute usage or shared runners usage @@ -123,7 +126,7 @@ Prerequisite: You can view the compute usage for a personal namespace: -1. On the top bar, in the upper-right corner, select your avatar. +1. On the left sidebar, select your avatar. 1. Select **Edit profile**. 1. On the left sidebar, select **Usage Quotas**. @@ -164,8 +167,8 @@ You can purchase additional units of compute for your group. You cannot transfer purchased units of compute from one group to another, so be sure to select the correct group. -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > Usage Quotas**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > Usage Quotas**. 1. Select **Pipelines**. 1. Select **Buy additional units of compute**. 1. Complete the details of the transaction. @@ -181,7 +184,7 @@ Prerequisite: To purchase additional units of compute for your personal namespace: -1. On the top bar, in the upper-right corner, select your avatar. +1. On the left sidebar, select your avatar. 1. Select **Edit profile**. 1. On the left sidebar, select **Usage Quotas**. 1. Select **Buy additional units of compute**. GitLab redirects you to the Customers Portal. diff --git a/doc/ci/pipelines/index.md b/doc/ci/pipelines/index.md index 258829cd5f7..c99df5b15e6 100644 --- a/doc/ci/pipelines/index.md +++ b/doc/ci/pipelines/index.md @@ -139,8 +139,8 @@ operation of the pipeline. To execute a pipeline manually: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **CI/CD > Pipelines**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Build > Pipelines**. 1. Select **Run pipeline**. 1. In the **Run for branch name or tag** field, select the branch or tag to run the pipeline for. 1. Enter any [CI/CD variables](../variables/index.md) required for the pipeline to run. @@ -349,8 +349,8 @@ Prerequisites: To trigger the pipeline when the upstream project is rebuilt: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > CI/CD**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > CI/CD**. 1. Expand **Pipeline subscriptions**. 1. Enter the project you want to subscribe to, in the format `<namespace>/<project>`. For example, if the project is `https://gitlab.com/gitlab-org/gitlab`, use `gitlab-org/gitlab`. diff --git a/doc/ci/pipelines/merge_trains.md b/doc/ci/pipelines/merge_trains.md index ffddaaf88cb..7bff13aa390 100644 --- a/doc/ci/pipelines/merge_trains.md +++ b/doc/ci/pipelines/merge_trains.md @@ -101,8 +101,8 @@ Prerequisites: To enable merge trains: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > Merge requests**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > Merge requests**. 1. In the **Merge method** section, verify that **Merge commit** is selected. 1. In the **Merge options** section: - In GitLab 13.6 and later, select **Enable merged results pipelines** and **Enable merge trains**. diff --git a/doc/ci/pipelines/merged_results_pipelines.md b/doc/ci/pipelines/merged_results_pipelines.md index 316d7819f55..16120924f37 100644 --- a/doc/ci/pipelines/merged_results_pipelines.md +++ b/doc/ci/pipelines/merged_results_pipelines.md @@ -41,8 +41,8 @@ To use merged results pipelines: To enable merged results pipelines in a project, you must have at least the Maintainer role: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > Merge requests**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +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 d08a511515f..49b129f11aa 100644 --- a/doc/ci/pipelines/schedules.md +++ b/doc/ci/pipelines/schedules.md @@ -26,8 +26,8 @@ Otherwise, the pipeline is not created. No error message is displayed. To add a pipeline schedule: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **CI/CD > Schedules**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +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, @@ -47,8 +47,8 @@ you must delete unused schedules before you can add another. The owner of a pipeline schedule can edit it: -1. On the top bar, select **Main menu > Projects** and find your project. -1. In the left sidebar, select **CI/CD > Schedules**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Build > Pipeline schedules**. 1. Next to the schedule, select **Edit** (**{pencil}**) and fill in the form. The user must have the Developer role or above for the project. If the user is @@ -60,8 +60,8 @@ of the schedule. To trigger a pipeline schedule manually, so that it runs immediately instead of the next scheduled time: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **CI/CD > Schedules**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. On the left sidebar, select **Build > Pipeline schedules**. 1. On the right of the list, for the pipeline you want to run, select **Play** (**{play}**). @@ -76,8 +76,8 @@ including [protected environments](../environments/protected_environments.md) an To take ownership of a pipeline created by a different user: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **CI/CD > Schedules**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. On the left sidebar, 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/development/internal_api/index.md b/doc/development/internal_api/index.md index 508976ea3a1..fc7cc3e21d3 100644 --- a/doc/development/internal_api/index.md +++ b/doc/development/internal_api/index.md @@ -665,7 +665,7 @@ The subscriptions endpoint is used by [CustomersDot](https://gitlab.com/gitlab-o ### Creating a subscription -Use a POST to create a subscription. +Use a POST command to create a subscription. ```plaintext POST /namespaces/:id/gitlab_subscription @@ -809,6 +809,107 @@ Example response: - CustomersDot +## Subscription add-on purchases (excluding storage and compute packs) + +The subscription add-on purchase endpoint is used by [CustomersDot](https://gitlab.com/gitlab-org/customers-gitlab-com) (`customers.gitlab.com`) to apply subscription add-on purchases like code suggestions for personal namespaces, or top-level groups within GitLab.com. It is not used to apply storage and compute pack purchases. + +### Create a subscription add-on purchase + +Use a POST to create a subscription add-on purchase. + +```plaintext +POST /namespaces/:id/subscription_add_on_purchase/:add_on_name +``` + +| Attribute | Type | Required | Description | +|:------------|:--------|:---------|:------------| +| `quantity` | integer | yes | Amount of units in the subscription add-on purchase (Example: Number of seats for a code suggestions add-on) | +| `expires_on` | date | yes | Expiration date of the subscription add-on purchase | +| `purchase_xid` | string | yes | Identifier for the subscription add-on purchase (Example: Subscription name for a code suggestions add-on) | + +Example request: + +```shell +curl --request POST --header "PRIVATE-TOKEN: <admin_access_token>" "https://gitlab.com/api/v4/namespaces/1234/subscription_add_on_purchase/code_suggestions?&quantity=10&expires_on="2024-07-15"&purchase_xid="A-S12345678"" +``` + +Example response: + +```json +{ + "namespace_id":1234, + "namespace_name":"A Namespace Name", + "add_on":"Code Suggestions", + "quantity":10, + "expires_on":"2024-07-15", + "purchase_xid":"A-S12345678" +} +``` + +### Update a subscription add-on purchases + +Use a PUT command to update an existing subscription add-on purchase. + +```plaintext +PUT /namespaces/:id/subscription_add_on_purchase/:add_on_name +``` + +| Attribute | Type | Required | Description | +|:------------|:--------|:---------|:------------| +| `quantity` | integer | yes | Amount of units in the subscription add-on purchase (Example: Number of seats for a code suggestions add-on) | +| `expires_on` | date | yes | Expiration date of the subscription add-on purchase | +| `purchase_xid` | string | yes | Identifier for the subscription add-on purchase (Example: Subscription name for a code suggestions add-on) | + +Example request: + +```shell +curl --request PUT --header "PRIVATE-TOKEN: <admin_access_token>" "https://gitlab.com/api/v4/namespaces/1234/subscription_add_on_purchase/code_suggestions?&quantity=15&expires_on="2024-07-15"&purchase_xid="A-S12345678"" +``` + +Example response: + +```json +{ + "namespace_id":1234, + "namespace_name":"A Namespace Name", + "add_on":"Code Suggestions", + "quantity":15, + "expires_on":"2024-07-15", + "purchase_xid":"A-S12345678" +} +``` + +### Retrieve a subscription add-on purchases + +Use a GET command to view an existing subscription add-on purchase. + +```plaintext +GET /namespaces/:id/subscription_add_on_purchase/:add_on_name +``` + +Example request: + +```shell +curl --header "PRIVATE-TOKEN: <admin_access_token>" "https://gitlab.com/api/v4/namespaces/1234/subscription_add_on_purchase/code_suggestions" +``` + +Example response: + +```json +{ + "namespace_id":1234, + "namespace_name":"A Namespace Name", + "add_on":"Code Suggestions", + "quantity":15, + "expires_on":"2024-07-15", + "purchase_xid":"A-S12345678" +} +``` + +### Known consumers + +- CustomersDot + ## Storage limit exclusions The namespace storage limit exclusion endpoints manage storage limit exclusions on top-level namespaces on GitLab.com. diff --git a/doc/user/enterprise_user/index.md b/doc/user/enterprise_user/index.md index b565c132f8b..36f698daf81 100644 --- a/doc/user/enterprise_user/index.md +++ b/doc/user/enterprise_user/index.md @@ -68,8 +68,11 @@ The custom domain must match the email domain exactly. For example, if your emai 1. In the upper-right corner, select **Add Domain**. 1. In **Domain**, enter the domain name. 1. In **Project**, link to a project. -1. Optional. In **Certificate**, switch the **Manually enter certificate information** toggle to add an SSL/TLS - certificate. You can also add the certificate and key later. +1. In **Certificate**: + - If you do not have or do not want to use an SSL certificate, leave **Automatic certificate management using Let's + Encrypt** selected. + - Optional. Turn on the **Manually enter certificate information** toggle to add an SSL/TLS certificate. You can also + add the certificate and key later. 1. Select **Add Domain**. NOTE: diff --git a/doc/user/group/access_and_permissions.md b/doc/user/group/access_and_permissions.md index 8aee3c06192..b7acded6720 100644 --- a/doc/user/group/access_and_permissions.md +++ b/doc/user/group/access_and_permissions.md @@ -46,8 +46,8 @@ configured by an administrator. To change the permitted Git access protocols for a group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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**. @@ -71,8 +71,8 @@ Administrators can combine restricted access by IP address with To restrict group access by IP address: -1. On the top bar, select **Main menu > Groups** and find your top-level group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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: @@ -112,8 +112,8 @@ You can prevent users with email addresses in specific domains from being added To restrict group access by domain: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Permissions and group features** section. 1. In the **Restrict membership by email** field, enter the domain names. 1. Select **Save changes**. @@ -156,8 +156,8 @@ If you prevent group sharing outside the hierarchy for the **Animals** group: To prevent sharing outside of the group's hierarchy: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand **Permissions and group features**. 1. Select **Members cannot invite groups outside of `<group_name>` and its subgroups**. 1. Select **Save changes**. @@ -172,8 +172,8 @@ which can be confusing and difficult to control. To restrict the permission to invite project members to a single source, prevent a project from being shared with other groups: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Permissions and group features** section. 1. Select **Projects in `<group_name>` cannot be shared with other groups**. 1. Select **Save changes**. @@ -186,10 +186,8 @@ added to a project lose access when the setting is enabled. As a group Owner, you can prevent non-members from requesting access to your group. -1. On the top bar, **Main menu > Groups** and find your group. -1. Select **Your Groups**. -1. Find the group and select it. -1. From the left menu, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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**. @@ -208,8 +206,8 @@ If even one is set to `true`, then the group does not allow outside forks. To prevent projects from being forked outside the group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Permissions and group features** section. 1. Check **Prevent project forking outside current group**. 1. Select **Save changes**. @@ -233,8 +231,9 @@ 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 top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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**. diff --git a/doc/user/group/clusters/index.md b/doc/user/group/clusters/index.md index 4c448d8e5c2..15fa5941dc2 100644 --- a/doc/user/group/clusters/index.md +++ b/doc/user/group/clusters/index.md @@ -21,8 +21,8 @@ your group, enabling you to use the same cluster across multiple projects. To view your group-level Kubernetes clusters: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Kubernetes**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Operate > Kubernetes**. ## Cluster management project @@ -89,8 +89,8 @@ your cluster, which can cause deployment jobs to fail. To clear the cache: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Kubernetes**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Operate > Kubernetes**. 1. Select your cluster. 1. Expand **Advanced settings**. 1. Select **Clear cluster cache**. diff --git a/doc/user/group/compliance_frameworks.md b/doc/user/group/compliance_frameworks.md index 5e76db35d5a..47764b0c915 100644 --- a/doc/user/group/compliance_frameworks.md +++ b/doc/user/group/compliance_frameworks.md @@ -16,8 +16,8 @@ requirements or needs additional oversight. The label can optionally enforce Compliance frameworks are created on top-level groups. Group owners can create, edit, and delete compliance frameworks: -1. On the top bar, select **Main menu > Groups > View all groups** and find your group. -1. On the left sidebar, select **Settings** > **General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings** > **General**. 1. Expand the **Compliance frameworks** section. 1. Create, edit, or delete compliance frameworks. @@ -40,8 +40,8 @@ A compliance framework that is set to default has a **default** label. Group owners can set a compliance framework as default (or remove the setting): -1. On the top bar, select **Main menu > Groups > View all groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Compliance frameworks** section and locate the compliance framework to set (or remove) as default. 1. Select the vertical ellipsis (**{ellipsis_v}**) for the compliance frame and then select **Set default** (or **Remove default**). @@ -125,8 +125,8 @@ Therefore, communicate with project users about compliance pipeline configuratio To configure a compliance pipeline: -1. On the top bar, select **Main menu > Groups > View all groups** and find your group. -1. On the left sidebar, select **Settings** > **General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings** > **General**. 1. Expand the **Compliance frameworks** section. 1. In **Compliance pipeline configuration (optional)**, add the 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/group/contribution_analytics/index.md b/doc/user/group/contribution_analytics/index.md index b0347ba5caa..02f1e7f21e2 100644 --- a/doc/user/group/contribution_analytics/index.md +++ b/doc/user/group/contribution_analytics/index.md @@ -20,8 +20,8 @@ Use contribution analytics data visualizations to: To view contribution analytics: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Analytics > Contribution**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Analyze > Contribution analytics**. Three bar charts and a table illustrate the number of contributions made by each group member: diff --git a/doc/user/group/devops_adoption/index.md b/doc/user/group/devops_adoption/index.md index c8b5b9be15b..7aa4695e58b 100644 --- a/doc/user/group/devops_adoption/index.md +++ b/doc/user/group/devops_adoption/index.md @@ -36,8 +36,8 @@ Prerequisite: To view DevOps Adoption: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Analytics > DevOps adoption** +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Analyze > DevOps adoption** ## DevOps Adoption categories @@ -80,8 +80,8 @@ twelve months. The chart only shows data from when you enabled DevOps Adoption f To view feature adoption over time: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Analytics > DevOps adoption**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Analyze > DevOps adoption**. 1. Select the **Overview** tab. Tooltips display information about the features tracked for individual months. diff --git a/doc/user/group/epics/epic_boards.md b/doc/user/group/epics/epic_boards.md index 6783e89779b..4a913c385a0 100644 --- a/doc/user/group/epics/epic_boards.md +++ b/doc/user/group/epics/epic_boards.md @@ -25,8 +25,8 @@ On the top of each list, you can see the number of epics in the list (**{epic}** To view an epic board: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Epics > Boards**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Plan > Epic boards**. ![GitLab epic board - Premium](img/epic_board_v15_10.png) @@ -38,8 +38,8 @@ Prerequisites: To create a new epic board: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Epics > Boards**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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. @@ -87,8 +87,8 @@ Prerequisites: To create a new list: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Epics > Boards**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Plan > Epic boards**. 1. In the upper-right corner, select **Create list**. 1. In the **New list** column expand the **Select a label** dropdown list and select the label to use as list scope. diff --git a/doc/user/group/epics/manage_epics.md b/doc/user/group/epics/manage_epics.md index 98316188496..9436ff317a7 100644 --- a/doc/user/group/epics/manage_epics.md +++ b/doc/user/group/epics/manage_epics.md @@ -205,8 +205,8 @@ Prerequisites: To view epics in a group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Epics**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Plan > Epics**. ### Who can view an epic @@ -250,8 +250,8 @@ You can filter the list of epics by: To filter: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Epics**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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 <kbd>Enter</kbd> on your keyboard. The list is filtered. diff --git a/doc/user/group/import/index.md b/doc/user/group/import/index.md index 5a3c9cf0e5a..0b9a1552281 100644 --- a/doc/user/group/import/index.md +++ b/doc/user/group/import/index.md @@ -136,10 +136,10 @@ To ensure GitLab maps users and their contributions correctly: Create the group you want to import to and connect the source GitLab instance: 1. Create either: - - A new group. On the top bar, select **{plus-square}**, then **New group**, and select **Import group**. + - A new group. On the left sidebar, at the top, select **Create new...** (**{plus}**) and **New group**. Then select **Import group**. - A new subgroup. On existing group's page, either: - Select **New subgroup**. - - On the top bar, Select **{plus-square}** and then **New subgroup**. Then on the left sidebar, select the **import an existing group** link. + - On the left sidebar, at the top, select **Create new...** (**{plus}**) and **New subgroup**. Then select the **import an existing group** link. 1. Enter the URL of a GitLab instance running GitLab 14.0 or later. 1. Enter the [personal access token](../../../user/profile/personal_access_tokens.md) for your source GitLab instance. 1. Select **Connect instance**. @@ -176,8 +176,7 @@ You can view all groups migrated by you by direct transfer listed on the group i To view group import history: 1. Sign in to GitLab. -1. On the top bar, select **Create new…** (**{plus-square}**). -1. Select **New group**. +1. On the left sidebar, at the top, select **Create new...** (**{plus}**) and **New group**. 1. Select **Import group**. 1. In the upper-right corner, select **History**. 1. If there are any errors for a particular import, you can see them by selecting **Details**. @@ -407,8 +406,8 @@ To solve this, you must change the source group path to include a non-numerical - The GitLab UI: - 1. On the top bar, select **Main menu > Groups** and find your group. - 1. On the left sidebar, select **Settings > General**. + 1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. + 1. Select **Settings > General**. 1. Expand **Advanced**. 1. Under **Change group URL**, change the group URL to include non-numeric characters. @@ -522,7 +521,8 @@ Prerequisite: To enable import and export for a group: -1. On the top bar, select **Main menu > Admin**. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **Admin Area**. 1. On the left sidebar, select **Settings > General**. 1. Expand **Visibility and access controls**. 1. In the **Import sources** section, select the checkboxes for the sources you want. @@ -535,9 +535,9 @@ Prerequisites: To export the contents of a group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. -1. In the **Advanced** section, select **Export Group**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. +1. In the **Advanced** section, select **Export group**. 1. After the export is generated, you should receive an email with a link to the [exported contents](#exported-contents) in a compressed tar archive, with contents in NDJSON format. 1. Alternatively, you can download the export from the UI: @@ -550,15 +550,13 @@ You can also export a group [using the API](../../../api/group_import_export.md) ### Import the group -1. Create a new group: - - On the top bar, select **Create new…** (**{plus-square}**) and then **New group**. - - On an existing group's page, select **New subgroup**. -1. Select **Import group**. +1. On the left sidebar, at the top, select **Create new...** (**{plus}**) and **New subgroup**. +1. Select the **import an existing group** link. 1. Enter your group name. 1. Accept or modify the associated group URL. -1. Select **Choose file**. +1. Select **Choose file...**. 1. Select the file that you exported in the [Export a group](#export-a-group) section. -1. To begin importing, select **Import group**. +1. To begin importing, select **Import**. Your newly imported group page appears after the operation completes. diff --git a/doc/user/group/index.md b/doc/user/group/index.md index 4119d94597b..4dbb05de584 100644 --- a/doc/user/group/index.md +++ b/doc/user/group/index.md @@ -47,22 +47,27 @@ the immediate parent group. ## View groups -To view groups, on the top bar, select **Main menu > Groups > View all groups**. +To explore all public groups: -The **Groups** page shows a list of groups, sorted by last updated date. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **View all your groups**. +1. At the top right, select **Explore groups**. -- To explore all public groups, select **Explore groups**. -- To view groups where you have a direct or indirect membership, select **Your groups**. This tab shows groups that you are a member of: - - Through membership of a subgroup's parent group. - - Through direct or inherited membership of a project in the group or subgroup. +To view groups where you have a direct or indirect membership: + +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **View all your groups**. + +This page shows groups that you are a member of: + +- Through membership of a subgroup's parent group. +- Through direct or inherited membership of a project in the group or subgroup. ## Create a group To create a group: -1. On the top bar, either: - - Select **Main menu > Groups > View all groups**, and on the right, select **New group**. - - To the left of the search box, select the plus sign and then **New group**. +1. On the left sidebar, at the top, select **Create new...** (**{plus}**) and **New group**. 1. Select **Create group**. 1. Enter a name for the group in **Group name**. For a list of words that cannot be used as group names, see [reserved names](../reserved_names.md). @@ -83,7 +88,7 @@ For details about groups, watch [GitLab Namespaces (users, groups and subgroups) To remove a group and its contents: -1. On the top bar, select **Main menu > Groups** and find your group. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. 1. On the left sidebar, select **Settings > General**. 1. Expand the **Advanced** section. 1. In the **Remove group** section, select **Remove group**. @@ -92,8 +97,8 @@ To remove a group and its contents: A group can also be removed from the groups dashboard: -1. On the top bar, select **Main menu > Groups > View all groups**. -1. Select **Your Groups**. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **View all your groups**. 1. Select (**{ellipsis_v}**) for the group you want to delete. 1. Select **Delete**. 1. In the Remove group section, select **Remove group**. @@ -120,8 +125,8 @@ Prerequisites: To immediately remove a group marked for deletion: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand **Advanced**. 1. In the "Permanently remove group" section, select **Remove group**. 1. Confirm the action when asked to. @@ -135,16 +140,18 @@ are deleted. To restore a group that is marked for deletion: -1. On the top bar, select **Main menu > Groups** and find your group. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. 1. Select **Settings > General**. -1. Expand the **Path, transfer, remove** section. +1. Expand the **Advanced** section. 1. In the Restore group section, select **Restore group**. ## Request access to a group As a user, you can request to be a member of a group, if an administrator allows it. -1. On the top bar, select **Main menu > Groups** and find your group. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **View all your groups**. +1. At the top right side, select **Explore groups**. 1. Under the group name, select **Request Access**. As many as ten of the most-recently-active group owners receive an email with your request. @@ -170,7 +177,8 @@ In lists of group members, entries can display the following badges: - **SAML**, to indicate the member has a [SAML account](saml_sso/index.md) connected to them. - **Enterprise**, to indicate that the member is an [enterprise user](../enterprise_user/index.md). -1. On the top bar, select **Main menu > Groups** and find your group. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Manage > Members**. 1. Above the list of members, in the **Filter members** box, enter filter criteria. - To view members in the group only, select **Membership = Direct**. - To view members of the group and its subgroups, select **Membership = Inherited**. @@ -182,7 +190,7 @@ In lists of group members, entries can display the following badges: You can search for members by name, username, or email. 1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. -1. On the left sidebar, 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 (**{search}**). @@ -191,7 +199,7 @@ You can search for members by name, username, or email. You can sort members by **Account**, **Access granted**, **Max role**, or **Last sign-in**. 1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. -1. On the left sidebar, 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 @@ -206,7 +214,7 @@ Prerequisite: - You must have the Owner role. 1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. -1. On the left sidebar, select **Manage > Members**. +1. Select **Manage > Members**. 1. Select **Invite members**. 1. Fill in the fields. - The role applies to all projects in the group. For more information, see [permissions](../permissions.md). @@ -232,8 +240,9 @@ Prerequisites: To remove a member from a group: 1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. -1. On the left sidebar, select **Manage > Members**. -1. Next to the member you want to remove, select **Remove member**. +1. Select **Manage > Members**. +1. Next to the member you want to remove, select the vertical ellipsis (**{ellipsis_v}**). +1. Select **Remove member**. 1. Optional. On the **Remove member** confirmation box: - To remove direct user membership from subgroups and projects, select the **Also remove direct user membership from subgroups and projects** checkbox. - To unassign the user from linked issues and merge requests, select the **Also unassign this user from linked issues and merge requests** checkbox. @@ -264,10 +273,8 @@ By default, users with at least the Developer role can create projects under a g To change this setting for a specific group: -1. On the top bar, select **Main menu > Groups > View all groups**. -1. Select **Your Groups**. -1. Find the group and select it. -1. From the left menu, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Permissions and group features** section. 1. Select the desired option in the **Roles allowed to create projects** dropdown list. 1. Select **Save changes**. diff --git a/doc/user/group/insights/index.md b/doc/user/group/insights/index.md index 17aa6cb9655..ab967c8b12c 100644 --- a/doc/user/group/insights/index.md +++ b/doc/user/group/insights/index.md @@ -23,8 +23,8 @@ Prerequisites: To access your group's insights: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Analytics > Insights**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Analyze > Insights**. ## Interact with insights charts @@ -65,9 +65,9 @@ To configure group insights: 1. Create a new file [`.gitlab/insights.yml`](../../project/insights/index.md#configure-project-insights) in a project that belongs to your group. -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. -1. Expand the **Analytics** tab and find the **Insights** section. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. +1. Expand **Analytics** and find the **Insights** section. 1. Select the project that contains your `.gitlab/insights.yml` configuration file. 1. Select **Save changes**. diff --git a/doc/user/group/issues_analytics/index.md b/doc/user/group/issues_analytics/index.md index dbade014ec2..cc43ca80801 100644 --- a/doc/user/group/issues_analytics/index.md +++ b/doc/user/group/issues_analytics/index.md @@ -15,8 +15,8 @@ prior. To access the chart: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Analytics > Issue Analytics**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. On the left sidebar, select **Analyze > Issue analytics**. Hover over each bar to see the total number of issues. diff --git a/doc/user/group/iterations/index.md b/doc/user/group/iterations/index.md index 9b246e6ad47..a4677182bb0 100644 --- a/doc/user/group/iterations/index.md +++ b/doc/user/group/iterations/index.md @@ -50,8 +50,8 @@ Prerequisites: To create an iteration cadence: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Issues > Iterations**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Plan > Iterations**. 1. Select **New iteration cadence**. 1. Enter the title and description of the iteration cadence. 1. To manually manage the iteration cadence, clear the **Enable automatic scheduling** checkbox and skip the next step. @@ -70,8 +70,8 @@ If you want to manually manage the created cadence, read [Manual Iteration Manag ### View the iterations list -1. On the top bar, select **Main menu > Groups** and find your group. -1. Select **Issues > Iterations**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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. @@ -91,8 +91,8 @@ Prerequisites: To edit an iteration cadence: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Issues > Iterations**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Plan > Iterations**. 1. Select **Edit iteration cadence**. When you use automatic scheduling and edit the **Automation start date** field, @@ -105,8 +105,8 @@ doesn't delete the eight existing upcoming iterations. #### Turn on and off automatic scheduling for an iteration cadence -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Issues > Iterations**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Plan > Iterations**. 1. Next to the cadence for which you want to turn on or off automatic scheduling, select the three-dot menu (**{ellipsis_v}**) **> Edit cadence**. 1. Select or clear the **Enable automatic scheduling** checkbox. @@ -157,8 +157,8 @@ Deleting an iteration cadence also deletes all iterations within that cadence. To delete an iteration cadence: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Issues > Iterations**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Plan > Iterations**. 1. Select the three-dot menu (**{ellipsis_v}**) > **Delete cadence** for the cadence you want to delete. 1. Select **Delete cadence**. @@ -178,8 +178,8 @@ Prerequisites: To create an iteration: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Issues > Iterations** and select an iteration cadence. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. On the left sidebar, select **Plan > Iterations** and select an iteration cadence. 1. Select **New iteration**. 1. Enter the title, a description (optional), a start date, and a due date. 1. Select **Create iteration**. The iteration details page opens. @@ -277,8 +277,8 @@ and get a more accurate understanding of scope attributable to each label. To group issues by label: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Issues > Iterations**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Plan > Iterations**. 1. In the **Group by** dropdown list, select **Label**. 1. Select the **Filter by label** dropdown list. 1. Select the labels you want to group by in the labels dropdown list. diff --git a/doc/user/group/manage.md b/doc/user/group/manage.md index e135964c6e6..aec4e026571 100644 --- a/doc/user/group/manage.md +++ b/doc/user/group/manage.md @@ -29,8 +29,8 @@ Prerequisite: To add a group README: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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. @@ -42,12 +42,12 @@ member with the Owner role. - As an administrator: 1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. - 1. On the left sidebar, 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, at the top, select **Search GitLab** (**{search}**) to find your group. - 1. On the left sidebar, 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. @@ -72,8 +72,8 @@ create a new group and transfer projects to it instead. To change your group path (group URL): -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General** page. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Advanced** section. 1. Under **Change group URL**, enter a new name. 1. Select **Change group URL**. @@ -120,7 +120,7 @@ To share a given group, for example, `Frontend` with another group, for example, `Engineering`: 1. Go to the `Frontend` group. -1. On the left sidebar, select **Manage > Members**. +1. Select **Manage > Members**. 1. Select **Invite a group**. 1. In the **Select a group to invite** list, select `Engineering`. 1. Select a [role](../permissions.md) as maximum access level. @@ -158,8 +158,8 @@ When transferring groups, note: To transfer a group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Advanced** section. 1. In the **Remove group** section, select **Transfer group**. 1. Select the group name in the drop down menu. @@ -173,8 +173,8 @@ You can disable all email notifications related to the group, which includes its To disable email notifications: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Permissions and group features** section. 1. Select **Email notifications are disabled**. 1. Select **Save changes**. @@ -193,8 +193,8 @@ This is particularly helpful for groups with a large number of users. To disable group mentions: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Permissions and group features** section. 1. Select **Group mentions are disabled**. 1. Select **Save changes**. @@ -237,9 +237,9 @@ Prerequisite: To specify a user cap: -1. On the top bar, select **Main menu > Groups** and find your group. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. You can set a cap on the top-level group only. -1. On the left sidebar, select **Settings > General**. +1. Select **Settings > General**. 1. Expand **Permissions and group features**. 1. In the **User cap** box, enter the desired number of users. 1. Select **Save changes**. @@ -259,8 +259,8 @@ Prerequisite: To remove the user cap: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand **Permissions and group features**. 1. In the **User cap** box, delete the value. 1. Select **Save changes**. @@ -280,7 +280,7 @@ Prerequisite: To approve members that are pending because they've exceeded the user cap: -1. On the top bar, select **Main menu > Groups** and find your group. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. 1. On the left sidebar, 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**. @@ -311,8 +311,8 @@ For more information, see [group-level project templates](custom_project_templat To enable group file templates: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Templates** section. 1. Choose a project to act as the template repository. 1. Select **Save changes**. @@ -344,8 +344,8 @@ Prerequisites: To enable this setting: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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. @@ -363,8 +363,8 @@ Prerequisite: To change this behavior: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand **Merge requests**. 1. Under **Merge checks**: - Select **Pipelines must succeed**. @@ -382,8 +382,8 @@ Prerequisite: To enable this setting: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand **Merge requests**. 1. Under **Merge checks**, select **All threads must be resolved**. 1. Select **Save changes**. @@ -400,8 +400,8 @@ that belong to the group. To view the merge request approval settings for a group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand the **Merge request approvals** section. 1. Select the settings you want. 1. Select **Save changes**. @@ -433,8 +433,8 @@ You can give all users in a group and its subgroups access to [Code Suggestions] To enable Code Suggestions for a group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand **Permissions and group features**. 1. Under **Code Suggestions**, select the **Projects in this group can use Code Suggestions** checkbox. 1. Select **Save changes**. @@ -454,8 +454,8 @@ that belong to the group. To enable Experiment features for a top-level group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand **Permissions and group features**. 1. Under **Experiment features**, select the **Use Experiment features** checkbox. 1. Select **Save changes**. @@ -474,8 +474,8 @@ that belong to the group. To enable third-party AI features for a group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand **Permissions and group features**. 1. Under **Third-party AI services**, select the **Use third-party AI services** checkbox. 1. Select **Save changes**. diff --git a/doc/user/group/repositories_analytics/index.md b/doc/user/group/repositories_analytics/index.md index c2a4d8175b3..e5ca41accfc 100644 --- a/doc/user/group/repositories_analytics/index.md +++ b/doc/user/group/repositories_analytics/index.md @@ -37,8 +37,8 @@ The **Analytics > Repositories** group page displays the average test coverage o To see the latest code coverage for each project in your group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Analytics > Repositories**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Analyze > Repository analytics**. 1. In the **Latest test coverage results** section, from the **Select projects** dropdown list, choose the projects you want to check. You can download code coverage data for specific projects using @@ -52,8 +52,8 @@ You can get a CSV of the code coverage data for all of the projects in your grou To get the report: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Analytics > Repositories**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Analyze > Repository analytics**. 1. Select **Download historic test coverage data (.csv)**. 1. Select the projects and date range you want to include in the report. 1. Select **Download test coverage data (.csv)**. diff --git a/doc/user/group/saml_sso/group_sync.md b/doc/user/group/saml_sso/group_sync.md index 430f2c4a69f..dd455944bf8 100644 --- a/doc/user/group/saml_sso/group_sync.md +++ b/doc/user/group/saml_sso/group_sync.md @@ -125,7 +125,8 @@ When global group memberships lock is enabled: To enable global group memberships lock: 1. [Configure SAML](../../../integration/saml.md) for your self-managed GitLab instance. -1. On the top bar, select **Main menu > Admin**. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **Admin Area**. 1. On the left sidebar, select **Settings > General**. 1. Expand the **Visibility and access controls** section. 1. Ensure the **Lock memberships to SAML synchronization** checkbox is selected. diff --git a/doc/user/group/saml_sso/index.md b/doc/user/group/saml_sso/index.md index cee393df680..5838b9821de 100644 --- a/doc/user/group/saml_sso/index.md +++ b/doc/user/group/saml_sso/index.md @@ -38,8 +38,8 @@ If you are having issues setting up your identity provider, see the To set up SSO with Azure as your identity provider: -1. In GitLab, on the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > SAML SSO**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > SAML SSO**. 1. Note the information on this page. 1. Go to Azure and [follow the instructions for configuring SSO for an application](https://learn.microsoft.com/en-us/azure/active-directory/manage-apps/add-application-portal-setup-sso). The following GitLab settings correspond to the Azure fields. @@ -71,8 +71,8 @@ For more information, see an [example configuration page](example_saml_config.md To set up Google Workspace as your identity provider: -1. In GitLab, on the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > SAML SSO**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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. @@ -115,8 +115,8 @@ 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. In GitLab, on the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > SAML SSO**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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/). @@ -152,8 +152,8 @@ OneLogin supports its own [GitLab (SaaS) application](https://onelogin.service-n To set up OneLogin as your identity provider: -1. In GitLab, on the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > SAML SSO**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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), @@ -179,8 +179,8 @@ To set up OneLogin as your identity provider: To configure some identity providers, you need a GitLab metadata URL. To find this URL: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > SAML SSO**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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. @@ -217,8 +217,8 @@ 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 top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > SAML SSO**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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. @@ -432,7 +432,7 @@ group owner, and then you can unlink the account. For example, to unlink the `MyOrg` account: -1. On the top bar, in the upper-right corner, select your avatar. +1. On the left sidebar, select your avatar. 1. Select **Edit profile**. 1. On the left sidebar, select **Account**. 1. In the **Service sign-in** section, select **Disconnect** next to the connected account. diff --git a/doc/user/group/saml_sso/scim_setup.md b/doc/user/group/saml_sso/scim_setup.md index e05c28bd3f7..e5d6c86a5ac 100644 --- a/doc/user/group/saml_sso/scim_setup.md +++ b/doc/user/group/saml_sso/scim_setup.md @@ -25,8 +25,8 @@ Prerequisites: To configure GitLab SAML SSO SCIM: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > SAML SSO**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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/settings/group_access_tokens.md b/doc/user/group/settings/group_access_tokens.md index 9dc01bc14f9..e264778062b 100644 --- a/doc/user/group/settings/group_access_tokens.md +++ b/doc/user/group/settings/group_access_tokens.md @@ -57,8 +57,8 @@ all projects that have visibility level set to [Internal](../../public_access.md To create a group access token: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > Access Tokens**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > Access Tokens**. 1. Enter a name. The token name is visible to any user with permissions to view the group. 1. Enter an expiry date for the token: - The token expires on that date at midnight UTC. @@ -119,8 +119,8 @@ or API. However, administrators can use a workaround: To revoke a group access token: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > Access Tokens**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > Access Tokens**. 1. Next to the group access token to revoke, select **Revoke**. ## Revoke a group access token using Rails console @@ -153,8 +153,8 @@ The scope determines the actions you can perform when you authenticate with a gr To enable or disable group access token creation for all subgroups in a top-level group: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +1. Select **Settings > General**. 1. Expand **Permissions and group features**. 1. Under **Permissions**, turn on or off **Users can create project access tokens and group access tokens in this group**. diff --git a/doc/user/group/subgroups/index.md b/doc/user/group/subgroups/index.md index 12d92196c50..81e972bf73b 100644 --- a/doc/user/group/subgroups/index.md +++ b/doc/user/group/subgroups/index.md @@ -56,7 +56,7 @@ the private subgroup. To view the subgroups of a group: -1. On the top bar, select **Main menu > Groups** and find your group. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. 1. Select the **Subgroups and projects** tab. 1. To view a nested subgroup, expand a subgroup in the hierarchy list. @@ -84,7 +84,7 @@ You cannot host a GitLab Pages subgroup website with a top-level domain name. Fo To create a subgroup: -1. On the top bar, select **Main menu > Groups** and find and select the parent group to add a subgroup to. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find a parent group for the subgroup. 1. On the parent group's overview page, in the upper-right corner, select **New subgroup**. 1. Select **Create group**. 1. Fill in the fields. View a list of [reserved names](../../reserved_names.md) that cannot be used as group names. @@ -99,13 +99,14 @@ Prerequisite: To change who can create subgroups on a group: - As a user with the Owner role on the group: - 1. On the top bar, select **Main menu > Groups** and find your group. - 1. On the left sidebar, select **Settings > General**. + 1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. + 1. Select **Settings > General**. 1. Expand **Permissions and group features**. 1. Select a role from **Roles allowed to create subgroups**. 1. Select **Save changes**. - As an administrator: - 1. On the top bar, select **Main menu > Admin**. + 1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). + 1. Select **Admin Area**. 1. On the left sidebar, select **Overview > Groups**. 1. In the group's row select **Edit**. 1. Select a role from **Allowed to create subgroups**. diff --git a/doc/user/group/value_stream_analytics/index.md b/doc/user/group/value_stream_analytics/index.md index f6df7eb33a2..952552fc648 100644 --- a/doc/user/group/value_stream_analytics/index.md +++ b/doc/user/group/value_stream_analytics/index.md @@ -209,10 +209,8 @@ Prerequisites: To view value stream analytics for your group or project: -1. On the top bar, select **Main menu**, and: - - For a project, select **Projects** and find your project. - - For a group, select **Groups** and find your group. -1. On the left sidebar, select **Analytics > Value stream**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group. +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. @@ -301,10 +299,8 @@ Prerequisite: To view key lifecycle metrics: -1. On the top bar, select **Main menu**, and: - - For a project, select **Projects** and find your project. - - For a group, select **Groups** and find your group. -1. On the left sidebar, select **Analytics > Value stream**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group. +1. Select **Analyze > Value stream analytics**. Key metrics display below the **Filter results** text box. 1. Optional. Filter the results: 1. Select the **Filter results** text box. @@ -317,10 +313,8 @@ To view key lifecycle metrics: To view the [Value Streams Dashboard](../../analytics/value_streams_dashboard.md) and [DORA metrics](../../analytics/dora_metrics.md): -1. On the top bar, select **Main menu**, and: - - For a project, select **Projects** and find your project. - - For a group, select **Groups** and find your group. -1. On the left sidebar, select **Analytics > Value stream**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group. +1. Select **Analyze > Value stream analytics**. 1. Below the **Filter results** text box, in the **Key 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`). @@ -334,10 +328,8 @@ 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 top bar, select **Main menu**, and: - - For a project, select **Projects** and find your project. - - For a group, select **Groups** and find your group. -1. On the left sidebar, select **Analytics > Value stream**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group. +1. Select **Analyze > Value stream analytics**. 1. Optional. Filter the results: 1. Select the **Filter results** text box. 1. Select a parameter. @@ -360,8 +352,8 @@ group and time frame. To view tasks by type: -1. On the top bar, select **Main menu > Groups** and find your group. -1. On the left sidebar, select **Analytics > Value stream**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your group. +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. To switch between the task type, select the **Settings** (**{settings}**) dropdown list and select **Issues** or **Merge Requests**. @@ -377,10 +369,8 @@ To view tasks by type: When you create a value stream, you can use GitLab default stages and hide or re-order them. You can also create custom stages in addition to those provided in the default template. -1. On the top bar, select **Main menu**, and: - - For a project, select **Projects** and find your project. - - For a group, select **Groups** and find your group. -1. On the left sidebar, select **Analytics > Value Stream**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group. +1. Select **Analyze > Value Stream analytics**. 1. Select **Create new Value Stream**. 1. Enter a name for the value stream. 1. Select **Create from default template**. @@ -403,10 +393,8 @@ If you have recently upgraded to GitLab Premium, it can take up to 30 minutes fo When you create a value stream, you can create and add custom stages that align with your own development workflows. -1. On the top bar, select **Main menu**, and: - - For a project, select **Projects** and find your project. - - For a group, select **Groups** and find your group. -1. On the left sidebar, select **Analytics > Value Stream**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group. +1. Select **Analyze > Value Stream analytics**. 1. Select **Create value stream**. 1. For each stage: - Enter a name for the stage. @@ -439,10 +427,8 @@ 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 top bar, select **Main menu**, and: - - For a project, select **Projects** and find your project. - - For a group, select **Groups** and find your group. -1. On the left sidebar, select **Analytics > Value Stream**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group. +1. Select **Analyze > Value Stream analytics**. 1. In the upper-right corner, select the dropdown list, then select a value stream. 1. Next to the value stream dropdown list, select **Edit**. 1. Optional: @@ -460,9 +446,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 top bar, select **Main menu**, and: - - For a project, select **Projects** and find your project. - - For a group, select **Groups** and find your group. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group. 1. In the upper-right corner, select the dropdown list, then select the value stream you would like to delete. 1. Select **Delete (name of value stream)**. 1. To confirm, select **Delete**. @@ -477,10 +461,8 @@ To delete a custom value stream: The **Total time chart** shows the average number of days it takes for development cycles to complete. The chart shows data for the last 500 workflow items. -1. On the top bar, select **Main menu**, and: - - For a project, select **Projects** and find your project. - - For a group, select **Groups** and find your group. -1. On the left sidebar, select **Analytics > Value stream**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project or group. +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/product_analytics/index.md b/doc/user/product_analytics/index.md index 0c875c549d0..0d97c008561 100644 --- a/doc/user/product_analytics/index.md +++ b/doc/user/product_analytics/index.md @@ -77,8 +77,9 @@ Prerequisite: - You must be an administrator of a self-managed GitLab instance. -1. On the top bar, select **Main menu > Admin**. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **Admin Area**. +1. Select **Settings > General**. 1. Expand the **Analytics** tab and find the **Product analytics** section. 1. Select **Enable product analytics** and enter the configuration values. 1. Select **Save changes**. @@ -93,8 +94,9 @@ Prerequisites: - Product analytics must be enabled at the instance-level. - You must have at least the Maintainer role for the project or group the project belongs to. -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > General**. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **Admin Area**. +1. Select **Settings > General** 1. Expand **Product Analytics**. 1. In the **Connect to your instance** section, enter the configuration values. 1. Select **Save changes**. diff --git a/doc/user/project/deploy_keys/index.md b/doc/user/project/deploy_keys/index.md index f7dc8079af8..ffe237825a7 100644 --- a/doc/user/project/deploy_keys/index.md +++ b/doc/user/project/deploy_keys/index.md @@ -62,8 +62,8 @@ To help detect a potential secret leak, you can use the To view the deploy keys available to a project: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > Repository**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > Repository**. 1. Expand **Deploy keys**. The deploy keys available are listed: @@ -80,8 +80,8 @@ Prerequisites: - [Generate an SSH key pair](../../ssh.md#generate-an-ssh-key-pair). Put the private SSH key on the host that requires access to the repository. -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > Repository**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > Repository**. 1. Expand **Deploy keys**. 1. Complete the fields. 1. Optional. To grant `read-write` permission, select the **Grant write permissions to this key** @@ -101,8 +101,9 @@ Prerequisites: To create a public deploy key: -1. On the top bar, select **Main menu > Admin**. -1. On the left sidebar, select **Deploy Keys**. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +1. Select **Admin Area**. +1. Select **Deploy Keys**. 1. Select **New deploy key**. 1. Complete the fields. - Use a meaningful description for **Name**. For example, include the name of the external host @@ -118,8 +119,8 @@ Prerequisites: To grant a public deploy key access to a project: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > Repository**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > Repository**. 1. Expand **Deploy keys**. 1. Select **Publicly accessible deploy keys**. 1. In the key's row, select **Enable**. @@ -138,8 +139,8 @@ Prerequisites: To disable a deploy key: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the left sidebar, select **Settings > Repository**. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. Select **Settings > Repository**. 1. Expand **Deploy keys**. 1. Select **Disable** (**{cancel}**). diff --git a/doc/user/project/time_tracking.md b/doc/user/project/time_tracking.md index bd935db6f02..9b5469f6cec 100644 --- a/doc/user/project/time_tracking.md +++ b/doc/user/project/time_tracking.md @@ -185,8 +185,8 @@ The following time units are available: In GitLab self-managed instances, you can limit the display of time units to hours. To do so: -1. On the top bar, select **Main menu > Admin**. -1. On the left sidebar, select **Settings > Preferences**. +1. On the left sidebar, expand the top-most chevron (**{chevron-down}**). +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/search/index.md b/doc/user/search/index.md index 4a0d9210913..2278da9a714 100644 --- a/doc/user/search/index.md +++ b/doc/user/search/index.md @@ -64,8 +64,8 @@ search, or choose a specific group or project. To search through code or other documents in a project: -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the top bar, in the search field, type the string you want to search for. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) and type the string you want to search for. 1. Press **Enter**. Code search shows only the first result in the file. @@ -122,8 +122,8 @@ To include archived projects with `search_projects_hide_archived` enabled, you m You can search for a commit SHA. -1. On the top bar, select **Main menu > Projects** and find your project. -1. On the top bar, in the search field, type the SHA. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) to find your project. +1. On the left sidebar, at the top, select **Search GitLab** (**{search}**) and type the SHA. If a single result is returned, GitLab redirects to the commit result and gives you the option to return to the search results page. |