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
..
activity.go
attachment.go
convert.go
git_commit_test.go
git_commit.go
issue_comment.go	Fix missed doer (#30231)	2024-04-08 21:26:41 +00:00
issue_test.go
issue.go
main_test.go
mirror.go
notification.go
package.go	Clarify permission "HasAccess" behavior (#30585)	2024-04-20 03:15:04 +00:00
pull_review_test.go
pull_review.go
pull_test.go
pull.go
release_test.go
release.go
repository.go
secret.go
status.go
user_test.go
user.go
utils_test.go
utils.go
wiki.go