IntenseWebs/gitea
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Explain that the no-access team unit does not affect public repositories (#22661)

Browse Source 
Fixes https://github.com/go-gitea/gitea/issues/22600

Add explanations to team unit access control.

---------

Co-authored-by: Jason Song <i@wolfogre.com>
This commit is contained in:
yp05327 2023-02-01 17:14:40 +09:00 committed by GitHub
parent 19d5b2f922
commit 72a83dcc82
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
options/locale/locale_en-US.ini
View File

@ -2432,7 +2432,7 @@ teams.leave.detail = Leave %s?
teams.can_create_org_repo = Create repositories teams.can_create_org_repo = Create repositories
teams.can_create_org_repo_helper = Members can create new repositories in organization. Creator will get administrator access to the new repository. teams.can_create_org_repo_helper = Members can create new repositories in organization. Creator will get administrator access to the new repository.
teams.none_access = No Access teams.none_access = No Access
teams.none_access_helper = Members cannot view or do any other action on this unit. teams.none_access_helper = Members cannot view or do any other action on this unit. It has no effect for public repositories.
teams.general_access = General Access teams.general_access = General Access
teams.general_access_helper = Members permissions will be decided by below permission table. teams.general_access_helper = Members permissions will be decided by below permission table.
teams.read_access = Read teams.read_access = Read