0
0
Fork 0
mirror of https://codeberg.org/forgejo/docs.git synced 2025-02-15 05:05:50 -05:00

minor: formatting, close forgejo/website#162

This commit is contained in:
Robert Wolff 2025-02-02 19:11:21 +01:00
parent 1b246b5040
commit 97a25d1214
2 changed files with 20 additions and 96 deletions

View file

@ -11,7 +11,7 @@ Besides their original purpose - reporting bugs to a project's maintainer -
they can be used to suggest enhancements, ask for new features, discuss a project's they can be used to suggest enhancements, ask for new features, discuss a project's
direction, ask questions and much more. direction, ask questions and much more.
### The Issue Tracker ## The Issue Tracker
![Issues list](../_images/user/issue-tracking-basics/issues-list.png) ![Issues list](../_images/user/issue-tracking-basics/issues-list.png)
@ -35,7 +35,7 @@ An issue can have an assignee, meaning someone responsible for resolving or mode
the issue. Their profile picture, with a link to their profile, can be seen in the issue the issue. Their profile picture, with a link to their profile, can be seen in the issue
list. list.
### Life of an Issue ## Life of an Issue
Once an issue in the Issue Tracker has been created, it will usually pass through a Once an issue in the Issue Tracker has been created, it will usually pass through a
process of review, discussion and closure, which can be more or less strictly defined, process of review, discussion and closure, which can be more or less strictly defined,
@ -59,9 +59,9 @@ something to them).
> If you encounter an abandoned project and there's no way of contacting the maintainer(s), > If you encounter an abandoned project and there's no way of contacting the maintainer(s),
> consider forking it, if you want to assume responsibility for it (or, rather, your fork). > consider forking it, if you want to assume responsibility for it (or, rather, your fork).
### Things to consider ## Things to consider
#### Security bugs ### Security bugs
If the bug you have found has security implications, **do not create If the bug you have found has security implications, **do not create
an issue right away!** Instead try contacting the project's maintainers privately. an issue right away!** Instead try contacting the project's maintainers privately.
@ -73,7 +73,7 @@ maintainer or ask for the address in the issue tracker.
> fixed _and_ the fixes are deployed**, because **otherwise, you might put the users of that > fixed _and_ the fixes are deployed**, because **otherwise, you might put the users of that
> project at severe risk**. > project at severe risk**.
#### Existing issues ### Existing issues
Before creating a new issue, please make sure that there isn't already an existing Before creating a new issue, please make sure that there isn't already an existing
issue about, i.e., the bug you want to report or the feature you want to request. issue about, i.e., the bug you want to report or the feature you want to request.
@ -84,7 +84,7 @@ if there is something more that you can contribute to it.
You should also make sure that the issue has not already been solved by having a look You should also make sure that the issue has not already been solved by having a look
at the closed issues **(3)** as well. at the closed issues **(3)** as well.
#### Try to be precise and helpful ### Try to be precise and helpful
Project maintainers love precise information about why, i.e., a bug is happening. Project maintainers love precise information about why, i.e., a bug is happening.
@ -95,7 +95,7 @@ If you can provide that information, it will be easier for the project maintaine
to quickly resolve your issue. And if you want it resolved even quicker, to quickly resolve your issue. And if you want it resolved even quicker,
consider writing a Pull Request solving the issue (if possible). consider writing a Pull Request solving the issue (if possible).
#### Be (reasonably) patient ### Be (reasonably) patient
Please remember that many project maintainers work on their free software projects Please remember that many project maintainers work on their free software projects
in their free time. Some maintainers may answer you within minutes, others within days. in their free time. Some maintainers may answer you within minutes, others within days.

View file

@ -30,95 +30,19 @@ By default, the person who creates a repository is an **_Owner_**.
The table below gives an overview of what collaborators are allowed to do when granted each of these permission levels: The table below gives an overview of what collaborators are allowed to do when granted each of these permission levels:
<table class="table"> | Task | Read | Write | Admin | Owner |
<thead> | ------------------------------------------------------------------------------------------------------------------------ | ---- | ----- | ----- | ----- |
<tr> | View, clone and pull repository | ✅ | ✅ | ✅ | ✅ |
<th scope="col"> Task </th> | Contribute pull requests | ✅ | ✅ | ✅ | ✅ |
<th scope="col"> Read </th> | Push to/update contributed pull requests | ✅ | ✅ | ✅ | ✅ |
<th scope="col"> Write</th> | Push directly to repository | ❌ | ✅ | ✅ | ✅ |
<th scope="col"> Admin </th> | Merge pull requests | ❌ | ✅ | ✅ | ✅ |
<th scope="col"> Owner </th> | Moderate/delete issues and comments | ❌ | ✅ | ✅ | ✅ |
</thead> | Force-push/rewrite history (if enabled) | ❌ | ✅ | ✅ | ✅ |
<tbody> | Add/remove collaborators to repository | ❌ | ❌ | ✅ | ✅ |
<tr> | Configure branch settings (protect/unprotect, enable force-push) | ❌ | ❌ | ✅ | ✅ |
<td scope="row"> View, clone and pull repository </td> | Configure repository settings (enable wiki, issues, PRs, releases, update profile) | ❌ | ❌ | ✅ | ✅ |
<td> <span style="color: green"></span> </td> | Configure repository settings in the danger zone (transfer ownership, delete wiki data / repository, archive repository) | ❌ | ❌ | ❌ | ✅ |
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
<tr>
<td scope="row"> Contribute pull requests </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
<tr>
<td scope="row"> Push to/update contributed pull requests </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
<tr>
<td scope="row"> Push directly to repository </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
<tr>
<td scope="row"> Merge pull requests </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
<tr>
<td scope="row"> Moderate/delete issues and comments </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
<tr>
<td scope="row"> Force-push/rewrite history (if enabled) </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
<tr>
<td scope="row"> Add/remove collaborators to repository </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
<tr>
<td scope="row"> Configure branch settings (protect/unprotect, enable force-push) </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
<tr>
<td scope="row"> Configure repository settings (enable wiki, issues, PRs, releases, update profile) </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: green"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
<tr>
<td scope="row"> Configure repository settings in the danger zone (transfer ownership, delete wiki data / repository, archive repository) </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: red"></span> </td>
<td> <span style="color: green"></span> </td>
</tr>
</tbody>
</table>
## Teams ## Teams