rework permission article
I think the article about (repo / org / team) permissions is outdated as of Gitea 1.16. Someone should check that it's still correct, or update it accordingly.
@fnetX The problem with the current page is that team permissions were updated to allow each "unit"(issues, code, wiki etc.) to have a different permission level. A certain team could have only write permissions to issues but have no access to other the units.
As for repo colloborates the page is still up-to-date, so it would only need to include a new section? for these unit permissions, as they are quite configurable and can really differ from the default permissions.
Yeah, I know. TBH, when I opened this issue, I expected that more stuff was changed upstream, but when writing the blog post I noticed it's not so much that needs changing. Still, I hope someone else finds the time to write about this. But recently, we haven't received much from the community, especially for the docs 🤷
Still, I hope someone else finds the time to write about this. But recently, we haven't received much from the community, especially for the docs 🤷
I will have a 👀 , codeberg is hosting my personal projects and my horrible code. The least I can do 😄
Thank you. Anyway, you are already contributing to Gitea, which is probably worth more than hosting a few MB of content 😉
Deleting a branch is permanent. It CANNOT be undone. Continue?