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 nitpicky punctuation edits

Browse source
This commit is contained in:
Zearin 2026-07-17 19:19:30 +02:00
parent 13db526474
commit 210df59880
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -37,7 +37,7 @@ it will seem as if it does not exist at all!
## Collaborators ## 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_**. 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> </thead>
<tbody> <tbody>
<tr> <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> <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> <td><span style="color: green">{% fas_icon "check" %}</span></td>
</tr> </tr>
<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: 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>
<td><span style="color: green">{% fas_icon "check" %}</span></td> <td><span style="color: green">{% fas_icon "check" %}</span></td>
@ -141,8 +141,8 @@ 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: 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. - 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)). - 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)). - 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. 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)). The team will have admin permissions (See the Admin column under [Collaborators](#collaborators)).
@ -151,7 +151,7 @@ Currently, there are six units that can be configured:
- Code: access source code, files, commits, and branches. - Code: access source code, files, commits, and branches.
- Issues: organize bug reports, tasks, and milestones. - Issues: organize bug reports, tasks, and milestones.
- Pull Requests: access pull requests, and code reviews. - Pull Requests: access pull requests and code reviews.
- Releases: track the project versions and downloads. - Releases: track the project versions and downloads.
- Wiki: access and write documentation. - Wiki: access and write documentation.
- Projects: access and manage issues and pull requests in project boards. - Projects: access and manage issues and pull requests in project boards.