Gusted 83cae67aa3 [SHARED] 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) (cherry picked from commit 93993029e4) (cherry picked from commit df3b058179) (cherry picked from commit 8ccc6b9cba) (cherry picked from commit 9fbe28fca3) (cherry picked from commit 4ef2be6dc7) https://codeberg.org/forgejo/forgejo/pulls/1873 Moved test from repo_test.go to forgejo_confirmation_repo_test.go to avoid conflicts.		2023-12-04 13:06:15 +01:00
..
api	[CLEANUP] Reuse ForgejoVersion variable	2023-12-04 12:47:02 +01:00
common	Clean up template locale usage (#27856)	2023-10-31 22:11:48 +08:00
install	[SECURITY] Rework long-term authentication	2023-12-04 12:47:02 +01:00
private	[CLI] implement forgejo-cli	2023-12-04 12:21:19 +01:00
utils	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
web	[SHARED] make confirmation clearer for dangerous actions	2023-12-04 13:06:15 +01:00
init.go	[API] Forgejo API /api/forgejo/v1	2023-12-04 12:47:01 +01:00