summaryrefslogtreecommitdiffstats
path: root/options
diff options
context:
space:
mode:
author0ko <0ko@noreply.codeberg.org>2024-12-12 05:08:24 +0100
committer0ko <0ko@noreply.codeberg.org>2024-12-12 05:08:24 +0100
commiteef45a73c96eb65c87539548212db177777c7d29 (patch)
tree0b43dcd39a9fc0b0f724f664d3ed147a4f95eb86 /options
parentMerge pull request 'Replace actions/setup-forgejo action with actions/setup-f... (diff)
downloadforgejo-eef45a73c96eb65c87539548212db177777c7d29.tar.xz
forgejo-eef45a73c96eb65c87539548212db177777c7d29.zip
branding: adjust mysql instruction
Diffstat (limited to 'options')
-rw-r--r--options/locale/locale_en-US.ini2
1 files changed, 1 insertions, 1 deletions
diff --git a/options/locale/locale_en-US.ini b/options/locale/locale_en-US.ini
index 91ff922026..4de4a5b81d 100644
--- a/options/locale/locale_en-US.ini
+++ b/options/locale/locale_en-US.ini
@@ -3495,7 +3495,7 @@ self_check.no_problem_found = No problem found yet.
self_check.database_collation_mismatch = Expect database to use collation: %s
self_check.database_collation_case_insensitive = Database is using a collation %s, which is an insensitive collation. Although Forgejo could work with it, there might be some rare cases which don't work as expected.
self_check.database_inconsistent_collation_columns = Database is using collation %s, but these columns are using mismatched collations. It might cause some unexpected problems.
-self_check.database_fix_mysql = For MySQL/MariaDB users, you could use the "gitea doctor convert" command to fix the collation problems, or you could also fix the problem by "ALTER ... COLLATE ..." SQLs manually.
+self_check.database_fix_mysql = For MySQL/MariaDB users, you could use the "forgejo doctor convert" command to fix the collation problems, or you could also fix the problem by "ALTER ... COLLATE ..." SQLs manually.
[action]
create_repo = created repository <a href="%s">%s</a>