Mirrors/gitea
0
0 Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-10-03 10:54:06 +02:00
Code Issues Activity

Fix various documentation, user-facing, and source comment typos (#16367)

Browse Source 
* Fix various doc, user-facing, and source comment typos

Found via `codespell -q 3 -S ./options/locale,./vendor -L ba,pullrequest,pullrequests,readby`
This commit is contained in:
luzpaz authored and GitHub committed 2021-07-08 13:38:13 +02:00
1 parent bc6f060b8c
commit e0296b6a6d
87 files changed
+132 -132
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/content/doc/help/faq.en-us.md
+1 -1
View File
@@ -142,7 +142,7 @@ The current way to achieve this is to create/modify a user with a max repo creat
Restricted users are limited to a subset of the content based on their organization/team memberships and collaborations, ignoring the public flag on organizations/repos etc.\_\_
Example use case: A company runs a Gitea instance that requires login. Most repos are public (accessible/browseable by all co-workers).
Example use case: A company runs a Gitea instance that requires login. Most repos are public (accessible/browsable by all co-workers).
At some point, a customer or third party needs access to a specific repo and only that repo. Making such a customer account restricted and granting any needed access using team membership(s) and/or collaboration(s) is a simple way to achieve that without the need to make everything private.