wxiaoguang 48d4580dd5 Clarify permission "HasAccess" behavior (#30585) ... Follow #30495 "HasAccess" behavior wasn't clear, to make it clear: * Use a new name `HasAnyUnitAccess`, it will be easier to review related code and permission problems. * Separate everyone access mode to a separate field, then all calls to HasAccess are reverted to old behavior before #30495. * Add new tests. --------- Co-authored-by: Giteabot <teabot@gitea.io>		2024-04-20 03:15:04 +00:00
..
actions
activities
admin
asymkey
auth
avatars
db
dbfs
fixtures	Add default board to new projects, remove uncategorized pseudo-board (#29874)	2024-03-27 20:54:32 +00:00
git
issues
migrations
organization
packages
perm	Clarify permission "HasAccess" behavior (#30585)	2024-04-20 03:15:04 +00:00
project
pull
repo
secret
shared/types
system
unit
unittest	Workaround to clean up old reviews on creating a new one (#28554)	2024-02-19 14:42:18 +01:00
user
webhook
error.go
fixture_generation.go
fixture_test.go
main_test.go
org_team_test.go
org_team.go	Clarify permission "HasAccess" behavior (#30585)	2024-04-20 03:15:04 +00:00
org_test.go	Add user blocking (#29028)	2024-03-04 08:16:03 +00:00
org.go
repo_test.go	Penultimate round of db.DefaultContext refactor (#27414)	2023-10-11 04:24:07 +00:00
repo_transfer.go
repo.go