Explain that the no-access team unit does not affect public repositor…

…ies (#22661) Fixes #22600 Add explanations to team unit access control. --------- Co-authored-by: Jason Song <[email protected]>
go-gitea · Feb 1, 2023 · 72a83dc · 72a83dc
1 parent 19d5b2f
commit 72a83dc
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/options/locale/locale_en-US.ini b/options/locale/locale_en-US.ini
@@ -2432,7 +2432,7 @@ teams.leave.detail = Leave %s?
 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.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_helper = Members permissions will be decided by below permission table.
 teams.read_access = Read