5 commits

Author	SHA1	Message	Date
Gusted	2457f5ff22	chore: branding import path (#7337) ... - Massive replacement of changing `code.gitea.io/gitea` to `forgejo.org`. - Resolves forgejo/discussions#258 Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/7337 Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org> Reviewed-by: Michael Kriese <michael.kriese@gmx.de> Reviewed-by: Beowulf <beowulf@beocode.eu> Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net> Co-authored-by: Gusted <postmaster@gusted.xyz> Co-committed-by: Gusted <postmaster@gusted.xyz>	2025-03-27 19:40:14 +00:00
0ko	469c214ec8	s/Gitea/Forgejo in various log messages and comments	2024-04-21 21:26:15 +05:00
Gusted	2d9afd0c21	[CHORE] Remove Microsoft SQL Server Support ... - Per https://codeberg.org/forgejo/discussions/issues/122	2024-04-05 23:37:36 +02:00
wxiaoguang	abb0294996	Partially enable MSSQL case-sensitive collation support (#29238) ... Follow #28662 (cherry picked from commit 29a8c8de779924694fadad80b31cc855dd62c0f2)	2024-03-11 23:36:59 +07: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