forgejo

mirror/forgejo

Fork 0

mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-11-10 12:15:43 +01:00

Commit graph

Author SHA1 Message Date

Author	SHA1	Message	Date
Lunny Xiao	15660334ba	Use tailwind instead of `gt-[wh]-` helper classes (#29423 ) Follow #29357 - Replace `gt-w-` -> `tw-w-` and remove `gt-w-` - Replace `gt-h-` -> `tw-h-` and remove `gt-h-` (cherry picked from commit 9a8c90ee18095d284192476834d5d23074d136f3) Conflicts: templates/base/head_navbar.tmpl templates/status/404.tmpl trivial context conflict	2024-03-06 12:10:43 +08:00
wxiaoguang	34a0684397	Improve CSS helper naming (#28769 ) * `gt-w-100` => `gt-w-full` to match tailwind * clarify `gt-hidden` priority	2024-01-12 20:28:01 +08: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

Lunny Xiao

15660334ba

Use tailwind instead of gt-[wh]- helper classes (#29423 )

Follow #29357
- Replace `gt-w-*` -> `tw-w-*` and remove `gt-w-*`
- Replace `gt-h-*` -> `tw-h-*` and remove `gt-h-*`

(cherry picked from commit 9a8c90ee18095d284192476834d5d23074d136f3)

Conflicts:
	templates/base/head_navbar.tmpl
	templates/status/404.tmpl
	trivial context conflict

2024-03-06 12:10:43 +08:00

wxiaoguang

34a0684397

Improve CSS helper naming (#28769 )

* `gt-w-100` => `gt-w-full` to match tailwind
* clarify `gt-hidden` priority

2024-01-12 20:28:01 +08: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

3 commits