Gusted b4bb9f8614 [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.		2023-09-18 20:41:30 +02:00
..
e2e	Update minimum password length requirements (#25946)	2023-08-21 19:27:50 +00:00
fuzz	Move fuzz tests into tests/fuzz (#22376)	2023-01-09 15:30:14 +08:00
gitea-lfs-meta	Test views of LFS files (#22196)	2022-12-23 07:41:56 +08:00
gitea-repositories-meta	Replace 'userxx' with 'orgxx' in all test files when the user type is org (#27052)	2023-09-14 02:59:53 +00:00
integration	[GITEA] Make confirmation clearer for dangerous actions	2023-09-18 20:41:30 +02:00
mssql.ini.tmpl	[CI] set PASSWORD_HASH_ALGO = argon2 for integration tests	2023-09-18 13:25:11 +02:00
mysql.ini.tmpl	[CI] set PASSWORD_HASH_ALGO = argon2 for integration tests	2023-09-18 13:25:11 +02:00
mysql8.ini.tmpl	[CI] set PASSWORD_HASH_ALGO = argon2 for integration tests	2023-09-18 13:25:11 +02:00
pgsql.ini.tmpl	[CI] set PASSWORD_HASH_ALGO = argon2 for integration tests	2023-09-18 13:25:11 +02:00
sqlite.ini.tmpl	[TESTS] increase test-sqlite log level to Trace	2023-09-18 14:00:11 +02:00
test_utils.go	Refactor tests (#26464)	2023-08-12 16:30:16 +00:00