diff options
Diffstat (limited to 'doc/development')
| -rw-r--r-- | doc/development/documentation/workflow.md | 2 | ||||
| -rw-r--r-- | doc/development/policies.md | 2 | ||||
| -rw-r--r-- | doc/development/testing_guide/end_to_end/index.md | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/development/documentation/workflow.md b/doc/development/documentation/workflow.md index ac21010dbad..a12af51e436 100644 --- a/doc/development/documentation/workflow.md +++ b/doc/development/documentation/workflow.md @@ -79,7 +79,7 @@ A member of the Technical Writing team adds these labels: ### Reviewing and merging -Anyone with the [Maintainer role](../../user/permissions.md) to the relevant GitLab project can +Anyone with the Maintainer role to the relevant GitLab project can merge documentation changes. Maintainers must make a good-faith effort to ensure that the content: - Is clear and sufficiently easy for the intended audience to navigate and understand. diff --git a/doc/development/policies.md b/doc/development/policies.md index ca5ca315f62..c9e4fdb4350 100644 --- a/doc/development/policies.md +++ b/doc/development/policies.md @@ -111,7 +111,7 @@ Each line represents a rule that was evaluated. There are a few things to note: Here you can see that the first four rules were evaluated `false` for which user and subject. For example, you can see in the last line that -the rule was activated because the user `john` had the Reporter [role](../user/permissions.md) on +the rule was activated because the user `john` had the Reporter role on `Project/4`. When a policy is asked whether a particular ability is allowed diff --git a/doc/development/testing_guide/end_to_end/index.md b/doc/development/testing_guide/end_to_end/index.md index 54287fc0993..dc989acbdcc 100644 --- a/doc/development/testing_guide/end_to_end/index.md +++ b/doc/development/testing_guide/end_to_end/index.md @@ -101,7 +101,7 @@ This is due to technical limitations in the GitLab permission model: the ability against a protected branch is controlled by the ability to push/merge to this branch. This means that for developers to be able to trigger a pipeline for the default branch in `gitlab-org/omnibus-gitlab`/`gitlab-org/gitlab-qa`, they would need to have the -[Maintainer role](../../../user/permissions.md) for those projects. +Maintainer role for those projects. For security reasons and implications, we couldn't open up the default branch to all the Developers. Hence we created these mirrors where Developers and Maintainers are allowed to push/merge to the default branch. This problem was discovered in <https://gitlab.com/gitlab-org/gitlab-qa/-/issues/63#note_107175160> and the "mirror" |