5 Commits

Author	SHA1	Message	Date
silverwind	a0160694b9	Enable nilnil linter for new code (#36591) ... Fixes: https://github.com/go-gitea/gitea/issues/36152 Enable the `nilnil` linter while adding `//nolint` comments to existing violations. This will ensure no new issues enter the code base while we can fix existing issues gradually. Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-16 09:57:18 +00:00
wxiaoguang	1c9b022c4d	Refactor db package and remove unnecessary DumpTables (#32930)	2024-12-20 16:11:38 +00:00
Lunny Xiao	696fbe6036	Refactor push mirror find and add check for updating push mirror (#32539) ... Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>	2024-11-18 05:59:04 +00:00
wxiaoguang	29a8c8de77	Partially enable MSSQL case-sensitive collation support (#29238) ... Follow #28662	2024-03-08 03:19:35 +00:00
wxiaoguang	2df7563f31	Recommend/convert to use case-sensitive collation for MySQL/MSSQL (#28662) ... Mainly for MySQL/MSSQL. It is important for Gitea to use case-sensitive database charset collation. If the database is using a case-insensitive collation, Gitea will show startup error/warning messages, and show the errors/warnings on the admin panel's Self-Check page. Make `gitea doctor convert` work for MySQL to convert the collations of database & tables & columns. * Fix #28131 ## ⚠️ BREAKING ⚠️ It is not quite breaking, but it's highly recommended to convert the database&table&column to a consistent and case-sensitive collation.	2024-01-10 11:03:23 +00:00