Codeberg/Documentation
42
199
Fork
You've already forked Documentation
161

rework permission article #204

Closed
opened 2022年02月26日 10:44:49 +01:00 by fnetX · 4 comments
Owner
Copy link

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.

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 added the due date 2022年03月09日 2022年02月26日 10:45:10 +01:00
fnetX modified the due date from 2022年03月09日 to 2022年03月17日 2022年03月03日 16:36:56 +01:00

@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.

@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.
Author
Owner
Copy link

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 🤷

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 😄

> 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 😄
Author
Owner
Copy link

Thank you. Anyway, you are already contributing to Gitea, which is probably worth more than hosting a few MB of content 😉

Thank you. Anyway, you are already contributing to Gitea, which is probably worth more than hosting a few MB of content 😉
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/major-cspell-monorepo
renovate/mstruebing-editorconfig-checker-3.x
renovate/lycheeverse-lychee-0.x
renovate/font-awesome
renovate/prettier-3.x
renovate/markdownlint-cli2-0.x
renovate/markdown-it-14.x
renovate/davidanson-markdownlint-cli2-0.x
renovate/pipelinecomponents-yamllint-0.x
renovate/11ty-eleventy-3.x
renovate/node-lts-slim
renovate/npm-pnpm-vulnerability
ci_pr_close_no_preview
pr-554
pr/554
gitea-icons-shortcode
No results found.
Labels
Clear labels
Codeberg Pages
Issues affecting Codeberg Pages
Documentation Usability
Issues related to using and reading docs.codeberg.org
Forgejo
Good First Issue! 👋
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Question
Kind: Security
Licensing
Part: Generator
This is related to the generation of the documentation, not to the content itself
Priority: High
The priority is high
Priority: Low
The priority is low
Priority: Medium
The priority is medium
Reviewed: Confirmed
Something has been confirmed
Reviewed: Duplicate
Something exists already
Reviewed: Invalid
Something was marked as invalid
Reviewed: Wontfix
Something won't be fixed
Status: Blocked
Status: Help wanted
Contributions are welcome!
Status: In progress
Work is in progress
Status: Needs feedback
Feedback is needed
Status: Ready for Review
Work is completed
Status: Review
Review is in progress / Reviewers wanted
Status: Stale
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2022年03月17日

Dependencies

No dependencies set.

Reference
Codeberg/Documentation#204
Reference in a new issue
Codeberg/Documentation
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?