diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-01-31 15:11:37 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-01-31 15:11:37 +0300 |
commit | c62dd5ae440db9ad4696000a863fbcb53fe83498 (patch) | |
tree | 3e4c18cd7a475e6d81f80335d173f1eb3f9510d8 /doc | |
parent | aa88b9053d72f3f9b69ae5365b77595dcae5c0c3 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc')
-rw-r--r-- | doc/operations/metrics/dashboards/develop.md | 8 | ||||
-rw-r--r-- | doc/operations/metrics/dashboards/yaml.md | 4 | ||||
-rw-r--r-- | doc/user/application_security/api_fuzzing/index.md | 2 | ||||
-rw-r--r-- | doc/user/application_security/dast_api/index.md | 2 | ||||
-rw-r--r-- | doc/user/ssh.md | 18 |
5 files changed, 26 insertions, 8 deletions
diff --git a/doc/operations/metrics/dashboards/develop.md b/doc/operations/metrics/dashboards/develop.md index da5a26fbffd..fe14ec1dc3d 100644 --- a/doc/operations/metrics/dashboards/develop.md +++ b/doc/operations/metrics/dashboards/develop.md @@ -18,19 +18,19 @@ commented-out examples you can use. ## Apply a dashboard template -Navigate to the browser-based editor of your choice: +Go to the browser-based editor of your choice: - In the **Repository view**: - 1. Navigate to **{doc-text}** **Repository > Files**. - 1. Select **{plus}** **Add to tree** and select **New file**, + 1. Go to **Repository > Files**. + 1. Select **Add to tree** and select **New file**, then select **Select a template type** to see a list of available templates: ![Metrics dashboard template selection](img/metrics_dashboard_template_selection_v13_3.png) - In the **[Web IDE](../../../user/project/web_ide/index.md)**: 1. Select **Web IDE** when viewing your repository. - 1. Select **{doc-new}** **New file**, then select **Choose a template** to see a list of available templates: + 1. Select **New file**, then select **Choose a template** to see a list of available templates: ![Metrics dashboard template selection WebIDE](img/metrics_dashboard_template_selection_web_ide_v13_3.png) ## Custom dashboard templates **(PREMIUM SELF)** diff --git a/doc/operations/metrics/dashboards/yaml.md b/doc/operations/metrics/dashboards/yaml.md index 68eddc6f087..7b0a91dd18a 100644 --- a/doc/operations/metrics/dashboards/yaml.md +++ b/doc/operations/metrics/dashboards/yaml.md @@ -149,8 +149,8 @@ This works by converting the value of `label` to lower-case and, if there are mo To confirm your dashboard definition contains valid YAML syntax: -1. Navigate to **{doc-text}** **Repository > Files**. -1. Navigate to your dashboard file in your repository. +1. Go to **Repository > Files**. +1. Go to your dashboard file in your repository. 1. Review the information pane about the file, displayed above the file contents. Files with valid syntax display **Metrics Dashboard YAML definition is valid**, diff --git a/doc/user/application_security/api_fuzzing/index.md b/doc/user/application_security/api_fuzzing/index.md index 0c05afac65f..b55c5a1b299 100644 --- a/doc/user/application_security/api_fuzzing/index.md +++ b/doc/user/application_security/api_fuzzing/index.md @@ -2026,7 +2026,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 **{shield}** **Security & Compliance > Vulnerability Report** + - In a project, go to the project's **Security & Compliance > 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/dast_api/index.md b/doc/user/application_security/dast_api/index.md index ca021e9f924..0cdbb879cfc 100644 --- a/doc/user/application_security/dast_api/index.md +++ b/doc/user/application_security/dast_api/index.md @@ -1941,7 +1941,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 **{shield}** **Security & Compliance > Vulnerability Report** + - In a project, go to the project's **Security & Compliance > 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. DAST API vulnerabilities are available in a section labeled diff --git a/doc/user/ssh.md b/doc/user/ssh.md index b71b120d246..0e4171decd8 100644 --- a/doc/user/ssh.md +++ b/doc/user/ssh.md @@ -377,6 +377,24 @@ git config core.sshCommand "ssh -o IdentitiesOnly=yes -i ~/.ssh/private-key-file This command does not use the SSH Agent and requires Git 2.10 or later. For more information on `ssh` command options, see the `man` pages for both `ssh` and `ssh_config`. +## View your account's SSH keys + +1. Sign in to GitLab. +1. On the top bar, in the top right corner, select your avatar. +1. Select **Preferences**. +1. On the left sidebar, select **SSH Keys**. + +Your existing SSH keys are listed at the bottom of the page. The information includes: + +- The key's: + - Name. + - Public fingerprint. + - Expiry date. + - Permitted usage types. +- The time a key was last used. On GitLab.com this value is unavailable, and you are unable to see if or when an SSH key has been used. For more information, see [issue 324764](https://gitlab.com/gitlab-org/gitlab/-/issues/324764). + +Select **Delete** to permanently delete an SSH key. + ## Use different accounts on a single GitLab instance You can use multiple accounts to connect to a single instance of GitLab. You |