wxiaoguang 50a72e7a83 Use a general approach to access custom/static/builtin assets (#24022) ... The idea is to use a Layered Asset File-system (modules/assetfs/layered.go) For example: when there are 2 layers: "custom", "builtin", when access to asset "my/page.tmpl", the Layered Asset File-system will first try to use "custom" assets, if not found, then use "builtin" assets. This approach will hugely simplify a lot of code, make them testable. Other changes: * Simplify the AssetsHandlerFunc code * Simplify the `gitea embedded` sub-command code --------- Co-authored-by: Jason Song <i@wolfogre.com> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>		2023-04-12 18:16:45 +08:00
..
collaborator.go
collaborator_test.go
commits.go
commits_test.go
create.go	Make label templates have consistent behavior and priority (#23749)	2023-04-10 16:44:02 +08:00
create_test.go
delete.go	Allow repo admins too to delete the repo (#23940)	2023-04-07 11:21:02 -04:00
env.go
fork.go
generate.go
generate_test.go
hooks.go
init.go	Use a general approach to access custom/static/builtin assets (#24022)	2023-04-12 18:16:45 +08:00
init_test.go	Make label templates have consistent behavior and priority (#23749)	2023-04-10 16:44:02 +08:00
main_test.go
push.go
repo.go
temp.go