Gusted 64e38b3363 [GITEA] Make confirmation clearer for dangerous actions ... - Currently the confirmation for dangerous actions such as transferring the repository or deleting it only requires the user to ~~copy paste~~ type the repository name. - This can be problematic when the user has a fork or another repository with the same name as an organization's repository, and the confirmation doesn't make clear that it could be deleting the wrong repository. While it's mentioned in the dialog, it's better to be on the safe side and also add the owner's name to be an element that has to be typed for these dangerous actions. - Added integration tests. (cherry picked from commit bf679b24dd) (cherry picked from commit 1963085dd9) (cherry picked from commit fb94095d19) (cherry picked from commit e1d1e46afe)		2023-10-09 20:12:05 +02:00
..
avatar.go
collaboration.go	Next round of db.DefaultContext refactor (#27089)	2023-09-16 14:39:12 +00:00
default_branch.go	Reduce usage of db.DefaultContext (#27073)	2023-09-14 17:09:32 +00:00
deploy_key.go	Another round of db.DefaultContext refactor (#27103) (#27262)	2023-09-25 19:24:35 +02:00
git_hooks.go
lfs.go
main_test.go
protected_branch.go	Update status and code index after changing the default branch (#27018)	2023-09-13 04:43:31 +00:00
protected_tag.go
runners.go	Fix repo count in org action settings (#27245) (#27353)	2023-09-29 20:00:24 +02:00
secrets.go	Fix repo count in org action settings (#27245) (#27353)	2023-09-29 20:00:24 +02:00
setting.go	[GITEA] Make confirmation clearer for dangerous actions	2023-10-09 20:12:05 +02:00
settings_test.go	More refactoring of db.DefaultContext (#27083)	2023-09-15 06:13:19 +00:00
variables.go	Fix repo count in org action settings (#27245) (#27353)	2023-09-29 20:00:24 +02:00
webhook.go