dallasgroot/Documentation
1
0
Fork 0
mirror of https://codeberg.org/Codeberg/Documentation.git synced 2026-08-15 14:53:29 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Minor copy-edits and formatting tweaks to Repo Permissions article (#849)

Browse source 
Just some trivial copy-edits to punctuation and formatting.

Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/849
Reviewed-by: Robert Wolff <mahlzahn@posteo.de>
This commit is contained in:
Zearin 2026-07-17 19:52:36 +02:00 committed by Robert Wolff
parent 13db526474
commit 539d032294
1 changed files with 14 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
content/collaborating/repo-permissions.md
View file

@ -37,7 +37,7 @@ it will seem as if it does not exist at all!
## Collaborators
There are four permission levels: **Read**, **Write**, **Administrator** and **Owner**.
There are four permission levels: **Read**, **Write**, **Administrator**, and **Owner**.
By default, the person who creates a repository is an **_Owner_**.
@ -55,7 +55,7 @@ The table below gives an overview of what collaborators are allowed to do when g
</thead>
<tbody>
<tr>
<td>View, clone and pull repository</td>
<td>View, clone, and pull repository</td>
<td><span style="color: green">{% fas_icon "check" %}</span></td>
<td><span style="color: green">{% fas_icon "check" %}</span></td>
<td><span style="color: green">{% fas_icon "check" %}</span></td>
@ -83,7 +83,7 @@ The table below gives an overview of what collaborators are allowed to do when g
<td><span style="color: green">{% fas_icon "check" %}</span></td>
</tr>
<tr>
<td>Merge pull requests </td>
<td>Merge pull requests</td>
<td><span style="color: red">{% fas_icon "times" %}</span></td>
<td><span style="color: green">{% fas_icon "check" %}</span></td>
<td><span style="color: green">{% fas_icon "check" %}</span></td>
@ -140,26 +140,26 @@ you can specify for each unit (Code Access, Issues, Releases) a different permis
Each unit is configured to have one of these 3 permission levels:
- No Access: Members cannot view or take any other action on this unit.
- Read: Members can view the unit, and do standard actions for that unit (See the Read column under [Collaborators](#collaborators)).
- Write: Members can view the unit, and execute write actions that unit (See the Write column under [Collaborators](#collaborators)).
- **No Access:** Members cannot view or take any other action on this unit.
- **Read:** Members can view the unit and do standard actions for that unit. (See the Read column under [Collaborators](#collaborators).)
- **Write:** Members can view the unit and execute write actions that unit. (See the Write column under [Collaborators](#collaborators).)
When a team is configured to have administrator access, when this is specified, you cannot change units.
The team will have admin permissions (See the Admin column under [Collaborators](#collaborators)).
Currently, there are six units that can be configured:
- Code: access source code, files, commits, and branches.
- Issues: organize bug reports, tasks, and milestones.
- Pull Requests: access pull requests, and code reviews.
- Releases: track the project versions and downloads.
- Wiki: access and write documentation.
- Projects: access and manage issues and pull requests in project boards.
- **Code:** access source code, files, commits, and branches.
- **Issues:** organize bug reports, tasks, and milestones.
- **Pull Requests:** access pull requests and code reviews.
- **Releases:** track the project versions and downloads.
- **Wiki:** access and write documentation.
- **Projects:** access/manage issues and pull requests in project boards.
There are also two units which can be toggled:
- External Wiki: access to external wiki.
- External Issues: access to the external issue tracker.
- **External Wiki:** access to external wiki.
- **External Issues:** access to the external issue tracker.
A team can be given the permission to create new repositories. When a member of such team creates a new repository,
they will get administrator access to the repository.