a649610d61
When creating a repo, the "FORCE_PRIVATE" config option should be respected, `readonly` doesn't work for checkbox, so it should use `disabled` attribute. (cherry picked from commit edbf74c418061b013a5855f604dd6be6baf34132) Conflicts: templates/repo/create.tmpl templates/repo/migrate/codebase.tmpl templates/repo/migrate/git.tmpl templates/repo/migrate/gitbucket.tmpl templates/repo/migrate/gitea.tmpl templates/repo/migrate/github.tmpl templates/repo/migrate/gitlab.tmpl templates/repo/migrate/gogs.tmpl templates/repo/migrate/onedev.tmpl already in forgejo fc0c5e80da Fix and improve repo visibility checkbox when FORCE_PRIVATE is on (#3786) enforcing FORCE_PRIVATE on repo settings was manually tested with a repository of an unprivileged user after setting FORCE_PRIVATE = true