Remove i18n backport tool at the moment because of translation format changed#36643
Merged
lunny merged 4 commits intogo-gitea:mainfrom Feb 17, 2026
Merged
Remove i18n backport tool at the moment because of translation format changed#36643lunny merged 4 commits intogo-gitea:mainfrom
lunny merged 4 commits intogo-gitea:mainfrom
Conversation
GiteaBot
added
the
lgtm/need 2
github-actions
bot
added
modifies/go
silverwind
approved these changes
Feb 16, 2026
GiteaBot
added
lgtm/need 1
Member
|
I searched the codebase for string |
Contributor
These are only test fixtures. They can use any filename. Ideally it should use "any-path/any-file.ext" to avoid misleading. |
lunny
changed the title
Zettat123
approved these changes
Feb 17, 2026
GiteaBot
added
lgtm/done
lunny
added
the
reviewed/wait-merge
GiteaBot
removed
the
reviewed/wait-merge
silverwind
added a commit
to silverwind/gitea
that referenced
this pull request
Feb 17, 2026
* origin/main: Remove i18n backport tool at the moment because of translation format changed (go-gitea#36643) Fix bug the protected branch rule name is conflicted with renamed branch name (go-gitea#36650) Update JS deps (go-gitea#36656)
silverwind
pushed a commit
to silverwind/gitea
that referenced
this pull request
Feb 18, 2026
… changed (go-gitea#36643) Starting with v1.26, Gitea uses a JSON configuration file format instead of the INI format used in v1.25 and earlier versions. Because of this fundamental format change, a clean translation backport to the v1.25 branch (or earlier release branches) is not feasible.The recommended approach is: - Wait until the release/v1.26 branch is created after the official v1.26 release. - Then introduce a new JSON-based configuration (or migration/compatibility layer) on top of that branch.
lunny
added a commit
that referenced
this pull request
Feb 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Starting with v1.26, Gitea uses a JSON configuration file format instead of the INI format used in v1.25 and earlier versions.
Because of this fundamental format change, a clean translation backport to the v1.25 branch (or earlier release branches) is not feasible.The recommended approach is: