Commit 93f6c7fb authored by intrigeri's avatar intrigeri
Browse files

GitLab: point to doc on our own GitLab

It will always match the version of GitLab we're using,
as opposed to whatever is published on docs.gitlab.com.
parent 824d0ced
...@@ -2,7 +2,7 @@ Tails issues are managed in [[!tails_gitlab "" desc="GitLab"]]. ...@@ -2,7 +2,7 @@ Tails issues are managed in [[!tails_gitlab "" desc="GitLab"]].
This page focuses on aspects of GitLab usage that are specific to Tails. This page focuses on aspects of GitLab usage that are specific to Tails.
For general GitLab usage information, see the For general GitLab usage information, see the
[GitLab user documentation](https://docs.gitlab.com/ce/user/). [[!tails_gitlab help/user desc="GitLab user documentation"]].
[[!toc levels=2]] [[!toc levels=2]]
...@@ -189,8 +189,8 @@ relationships between issues. Here is how we can overcome these limitations. ...@@ -189,8 +189,8 @@ relationships between issues. Here is how we can overcome these limitations.
### Parent/subtask and Blocks relationship ### Parent/subtask and Blocks relationship
A GitLab issue can have a [task A GitLab issue can have a
list](https://docs.gitlab.com/ce/user/markdown.html#task-lists). [[!tails_gitlab help/user/markdown.html#task-lists desc="task list"]].
Every task is a task list can be: Every task is a task list can be:
...@@ -209,14 +209,15 @@ referenced issue, with a link to the referencing issue. ...@@ -209,14 +209,15 @@ referenced issue, with a link to the referencing issue.
## Confidential issues ## Confidential issues
You can make an issue You can make an issue
[confidential](https://docs.gitlab.com/ce/user/project/issues/confidential_issues.html) [[!tails_gitlab help/user/project/issues/confidential_issues.html desc="confidential"]]
when creating it or at any later time. when creating it or at any later time.
A confidential issue is visible only by: A confidential issue is visible only by:
- whoever created it - whoever created it
- project members with at least - project members with at least
[Reporter](https://docs.gitlab.com/ce/user/permissions.html#project-members-permissions) [[!tails_gitlab help/user/permissions.html#project-members-permissions
desc="Reporter"]]
access; that is, for our [[!tails_gitlab tails/tails desc="main GitLab access; that is, for our [[!tails_gitlab tails/tails desc="main GitLab
project"]]: most past and present Tails contributors project"]]: most past and present Tails contributors
...@@ -279,9 +280,9 @@ you can: ...@@ -279,9 +280,9 @@ you can:
- Stay informed of what's happening in GitLab - Stay informed of what's happening in GitLab
To do so, enable email To do so, enable email
[notifications](https://docs.gitlab.com/ce/user/profile/notifications.html). [[!tails_gitlab help/user/profile/notifications.html desc="notifications"]].
- Participate in [discussions](https://docs.gitlab.com/ce/user/discussions/) - Participate in [[!tails_gitlab help/user/discussions/ desc="discussions"]]
on issues and merge requests, modify issues metadata on issues and merge requests, modify issues metadata
To do so, reply to an email notification you've received from GitLab. To do so, reply to an email notification you've received from GitLab.
...@@ -291,13 +292,13 @@ you can: ...@@ -291,13 +292,13 @@ you can:
In particular: In particular:
- Write your email in - Write your email in
[Markdown](https://docs.gitlab.com/ce/user/markdown.html). [[!tails_gitlab help/user/markdown.html Markdown]].
- You can use - You can use
[Quick actions](https://docs.gitlab.com/ce/user/project/quick_actions.html). [[!tails_gitlab help/user/project/quick_actions.html desc="Quick actions"]].
- Create new issues - Create new issues
See [New issue via email](https://docs.gitlab.com/ce/user/project/issues/managing_issues.html#new-issue-via-email) See [[!tails_gitlab help/user/project/issues/managing_issues.html#new-issue-via-email desc="New issue via email"]]
in the GitLab documentation. in the GitLab documentation.
# Core teams' work # Core teams' work
...@@ -423,15 +424,16 @@ implemented](https://salsa.debian.org/tails-team/gitlab-migration/issues/33). ...@@ -423,15 +424,16 @@ implemented](https://salsa.debian.org/tails-team/gitlab-migration/issues/33).
#### Relevant GitLab doc #### Relevant GitLab doc
- [Permissions](https://docs.gitlab.com/ee/user/permissions.html) - [[!tails_gitlab help/user/permissions.html desc="Permissions"]]
- [Authorization for Merge requests](https://docs.gitlab.com/ce/user/project/merge_requests/authorization_for_merge_requests.html) - [[!tails_gitlab help/user/project/merge_requests/authorization_for_merge_requests.html desc="Authorization for Merge requests"]]
- [Protected Branches](https://docs.gitlab.com/ce/user/project/protected_branches.html) - [[!tails_gitlab help/user/project/protected_branches.html desc="Protected Branches"]]
- [Groups](https://docs.gitlab.com/ee/user/group/) - [[!tails_gitlab help/user/group/ desc="Groups"]]
#### Access levels #### Access levels
We use the [Protected branch We use the [[!tails_gitlab
flow](https://docs.gitlab.com/ce/user/project/merge_requests/authorization_for_merge_requests.html#protected-branch-flow): help/user/project/merge_requests/authorization_for_merge_requests.html#protected-branch-flow
desc="Protected branch flow"]]:
- Our major branches and release tags are marked as "Protected". - Our major branches and release tags are marked as "Protected".
- Committers get "Maintainer" access. - Committers get "Maintainer" access.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment