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
..
upload
access_log.go
api_org.go
api_test.go
api.go	Refactor cache and disable go-chi cache (#30417)	2024-04-13 08:38:44 +00:00
base_test.go
base.go
captcha.go	Refactor cache and disable go-chi cache (#30417)	2024-04-13 08:38:44 +00:00
context_cookie.go
context_model.go
context_request.go
context_response.go	Refactor URL detection (#29960)	2024-03-21 12:02:34 +00:00
context_template.go
context_test.go	Refactor external URL detection (#29973)	2024-03-22 04:32:40 +08:00
context.go	Refactor web routes (#30519)	2024-04-17 08:31:37 +00:00
csrf.go
org.go
package.go
pagination.go
permission.go
private.go
repo.go	Clarify permission "HasAccess" behavior (#30585)	2024-04-20 03:15:04 +00:00
response.go
user.go
utils.go
xsrf_test.go
xsrf.go