docs(agents): require translations when source strings change - #557
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
This was referenced Jul 25, 2026
phil-davis
reviewed
Jul 26, 2026
phil-davis
left a comment
phil-davis
left a comment
Contributor
There was a problem hiding this comment.
How will an ordinary person be able to know what is the correct translation for each language when making a PR to change some text, or add a new feature that has front-end UI text added?
Member
Author
|
We will provide a proper AI skill. Research ongoing. |
phil-davis
approved these changes
Jul 26, 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
2 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.
Adds a Translations rule to
agents.mdso AI agents and contributors keep thel10n/catalogs in sync whenever translatable source strings change.Why
Translations are moving from Transifex to in-repo maintenance (see companion PR retiring the Transifex sync). This codifies the new expectation: a source-string change must carry its translation updates in the same PR.
Change
New
### Translationssubsection under## OSPO Policy Constraints:$l->t()/p()intemplates/,t()/n()injs/) must update everyl10n/<lang>.js+.json..js/.jsonpairs in sync; preserve each file'spluralForm; plural arrays need one element pernplurals.🤖 Generated with Claude Code