gitea/services/forms
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.go
auth_form.go
org.go Allow Organisations to have a E-Mail (#25082) 2023-07-25 08:26:27 +00:00
package_form.go
repo_branch_form.go
repo_form_test.go
repo_form.go 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
repo_tag_form.go
runner.go Support changing labels of Actions runner without re-registration (#24806) 2023-06-13 22:28:31 +08:00
user_form_auth_openid.go
user_form_hidden_comments.go Less naked returns (#25713) 2023-07-07 05:31:56 +00:00
user_form_test.go Redesign Scoped Access Tokens (#24767) 2023-06-04 20:57:16 +02:00
user_form.go Fix required error for token name (#28267) 2023-11-29 03:47:05 +00:00