wxiaoguang eedb8f4129 Only use supported sort order for "explore/users" page (#29430) ... Thanks to inferenceus : some sort orders on the "explore/users" page could list users by their lastlogintime/updatetime. It leaks user's activity unintentionally. This PR makes that page only use "supported" sort orders. Removing the "sort orders" could also be a good solution, while IMO at the moment keeping the "create time" and "name" orders is also fine, in case some users would like to find a target user in the search result, the "sort order" might help. 		2024-02-27 17:10:51 +08:00
..
e2e	Require MySQL 8.0, PostgreSQL 12, MSSQL 2012 (#27337)	2023-10-03 13:27:57 -04:00
fuzz	Rework markup link rendering (#26745)	2024-01-15 08:49:24 +00:00
gitea-lfs-meta	Test views of LFS files (#22196)	2022-12-23 07:41:56 +08:00
gitea-repositories-meta	Allow non-admin users to delete review requests (#29057)	2024-02-24 12:38:43 +00:00
integration	Only use supported sort order for "explore/users" page (#29430)	2024-02-27 17:10:51 +08:00
testdata/data/attachments/a/0	Allow get release download files and lfs files with oauth2 token format (#26430)	2023-10-01 10:41:52 +00:00
mssql.ini.tmpl	Disable query token param in integration tests (#28592)	2023-12-23 11:29:51 +08:00
mysql.ini.tmpl	Disable query token param in integration tests (#28592)	2023-12-23 11:29:51 +08:00
pgsql.ini.tmpl	Disable query token param in integration tests (#28592)	2023-12-23 11:29:51 +08:00
sqlite.ini.tmpl	Disable query token param in integration tests (#28592)	2023-12-23 11:29:51 +08:00
test_utils.go	Allow get release download files and lfs files with oauth2 token format (#26430)	2023-10-01 10:41:52 +00:00