From 97a25d12144ad6313915876da539a9a00e5d105c Mon Sep 17 00:00:00 2001 From: Robert Wolff Date: Sun, 2 Feb 2025 19:11:21 +0100 Subject: [PATCH] minor: formatting, close forgejo/website#162 --- docs/user/issue-tracking-basics.md | 14 ++-- docs/user/repo-permissions.md | 102 ++++------------------------- 2 files changed, 20 insertions(+), 96 deletions(-) diff --git a/docs/user/issue-tracking-basics.md b/docs/user/issue-tracking-basics.md index 832108d4..cb7791c3 100644 --- a/docs/user/issue-tracking-basics.md +++ b/docs/user/issue-tracking-basics.md @@ -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 direction, ask questions and much more. -### The Issue Tracker +## The Issue Tracker ![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 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 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), > 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 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 > project at severe risk**. -#### Existing issues +### Existing issues 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. @@ -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 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. @@ -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, 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 in their free time. Some maintainers may answer you within minutes, others within days. diff --git a/docs/user/repo-permissions.md b/docs/user/repo-permissions.md index d0e8fb76..1b6f64ff 100644 --- a/docs/user/repo-permissions.md +++ b/docs/user/repo-permissions.md @@ -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: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Task Read Write Admin Owner
View, clone and pull repository ✅ ✅ ✅ ✅
Contribute pull requests ✅ ✅ ✅ ✅
Push to/update contributed pull requests ✅ ✅ ✅ ✅
Push directly to repository ❌ ✅ ✅ ✅
Merge pull requests ❌ ✅ ✅ ✅
Moderate/delete issues and comments ❌ ✅ ✅ ✅
Force-push/rewrite history (if enabled) ❌ ✅ ✅ ✅
Add/remove collaborators to repository ❌ ❌ ✅ ✅
Configure branch settings (protect/unprotect, enable force-push) ❌ ❌ ✅ ✅
Configure repository settings (enable wiki, issues, PRs, releases, update profile) ❌ ❌ ✅ ✅
Configure repository settings in the danger zone (transfer ownership, delete wiki data / repository, archive repository) ❌ ❌ ❌ ✅
+| Task | Read | Write | Admin | Owner | +| ------------------------------------------------------------------------------------------------------------------------ | ---- | ----- | ----- | ----- | +| View, clone and pull repository | ✅ | ✅ | ✅ | ✅ | +| Contribute pull requests | ✅ | ✅ | ✅ | ✅ | +| Push to/update contributed pull requests | ✅ | ✅ | ✅ | ✅ | +| Push directly to repository | ❌ | ✅ | ✅ | ✅ | +| Merge pull requests | ❌ | ✅ | ✅ | ✅ | +| Moderate/delete issues and comments | ❌ | ✅ | ✅ | ✅ | +| Force-push/rewrite history (if enabled) | ❌ | ✅ | ✅ | ✅ | +| Add/remove collaborators to repository | ❌ | ❌ | ✅ | ✅ | +| Configure branch settings (protect/unprotect, enable force-push) | ❌ | ❌ | ✅ | ✅ | +| Configure repository settings (enable wiki, issues, PRs, releases, update profile) | ❌ | ❌ | ✅ | ✅ | +| Configure repository settings in the danger zone (transfer ownership, delete wiki data / repository, archive repository) | ❌ | ❌ | ❌ | ✅ | ## Teams