diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-12 03:22:18 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-12 03:22:18 +0300 |
commit | 101d32c3b8d57c73088f1103f87899b0b20531eb (patch) | |
tree | 743e32b7b63be5ce60b28ff0caccedaff65e9fdc /doc/user/project/deploy_keys | |
parent | 6d08f67e10d01b6198daaad31b402e54bfe068e8 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/user/project/deploy_keys')
-rw-r--r-- | doc/user/project/deploy_keys/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/user/project/deploy_keys/index.md b/doc/user/project/deploy_keys/index.md index d7b6f1ffc6c..6c2d4763526 100644 --- a/doc/user/project/deploy_keys/index.md +++ b/doc/user/project/deploy_keys/index.md @@ -65,7 +65,7 @@ As with all sensitive information, you should ensure only those who need access For human interactions, use credentials tied to users such as Personal Access Tokens. To help detect a potential secret leak, you can use the -[Audit Event](../../../administration/audit_event_streaming/examples.md#example-payloads-for-ssh-events-with-deploy-key) feature. +[Audit Event](../../../administration/audit_event_streaming/examples.md#example-payloads-for-git-over-ssh-events-with-deploy-key) feature. ## View deploy keys |