diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-19 12:08:42 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-08-19 12:08:42 +0300 |
| commit | b76ae638462ab0f673e5915986070518dd3f9ad3 (patch) | |
| tree | bdab0533383b52873be0ec0eb4d3c66598ff8b91 /doc/development/reference_processing.md | |
| parent | 434373eabe7b4be9593d18a585fb763f1e5f1a6f (diff) | |
Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42
Diffstat (limited to 'doc/development/reference_processing.md')
| -rw-r--r-- | doc/development/reference_processing.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/development/reference_processing.md b/doc/development/reference_processing.md index 2fd0ce51b39..ad6552e88fe 100644 --- a/doc/development/reference_processing.md +++ b/doc/development/reference_processing.md @@ -152,7 +152,8 @@ a resource that some subsequent readers should not be able to see. For example, you might create an issue, and refer to a confidential issue `#1234`, which you have access to. This is rendered in the cached HTML as a link to -that confidential issue, with data attributes containing its ID, the ID of the +that [confidential issue](../user/project/issues/confidential_issues.md), +with data attributes containing its ID, the ID of the project and other confidential data. A later reader, who has access to your issue might not have permission to read issue `#1234`, and so we need to redact these sensitive pieces of data. This is what `ReferenceParser` classes do. |