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
..
action.go
avatar.go
blob.go
branch.go
collaborators.go
commits.go
compare.go
file.go
fork.go
git_hook.go
git_ref.go
hook_test.go
hook.go
issue_attachment.go
issue_comment_attachment.go
issue_comment.go
issue_dependency.go
issue_label.go
issue_pin.go
issue_reaction.go
issue_stopwatch.go
issue_subscription.go
issue_tracked_time.go
issue.go
key.go
label.go
language.go
main_test.go
migrate.go
milestone.go
mirror.go
notes.go
patch.go
pull_review.go
pull.go
release_attachment.go
release_tags.go
release.go
repo_test.go
repo.go	Clarify permission "HasAccess" behavior (#30585)	2024-04-20 03:15:04 +00:00
runners.go
star.go
status.go
subscriber.go
tag.go
teams.go
topic.go
transfer.go
tree.go
wiki.go