Lunny Xiao c08d263a19 Remove trust model selection from repository creation on web page because it can be changed in settings later (#28814) ... As more and more options can be set for creating the repository, I don't think we should put all of them into the creation web page which will make things look complicated and confusing. And I think we need some rules about how to decide which should/should not be put in creating a repository page. One rule I can imagine is if this option can be changed later and it's not a MUST on the creation, then it can be removed on the page. So I found trust model is the first one. This PR removed the trust model selections on creating a repository web page and kept others as before. This is also a preparation for #23894 which will add a choice about SHA1 or SHA256 that cannot be changed once the repository created.		2024-01-16 20:54:48 +08:00
..
admin	Forbid removing the last admin user (#28337)	2024-01-15 06:51:43 +00:00
auth	Normalize oauth email username (#28561)	2024-01-03 18:48:20 -06:00
devtest
events
explore
feed	Rework markup link rendering (#26745)	2024-01-15 08:49:24 +00:00
healthcheck
misc	Refactor CORS handler (#28587)	2023-12-25 20:13:18 +08:00
org	Rework markup link rendering (#26745)	2024-01-15 08:49:24 +00:00
repo	Remove trust model selection from repository creation on web page because it can be changed in settings later (#28814)	2024-01-16 20:54:48 +08:00
shared	Rework markup link rendering (#26745)	2024-01-15 08:49:24 +00:00
user	Rework markup link rendering (#26745)	2024-01-15 08:49:24 +00:00
base.go
githttp.go	Refactor CORS handler (#28587)	2023-12-25 20:13:18 +08:00
goget.go
home.go
metrics.go
nodeinfo.go
swagger_json.go
web.go	Recommend/convert to use case-sensitive collation for MySQL/MSSQL (#28662)	2024-01-10 11:03:23 +00:00
webfinger.go