Skip to content

docs(agents): require translations when source strings change #557

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DeepDiver1975 merged 1 commit into from
Jul 26, 2026
Merged

docs(agents): require translations when source strings change #557

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions agents.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,11 @@ make dist # Create distribution package
- Review and merge Dependabot PRs as part of regular maintenance.
- Do not introduce new dependencies without discussion in an issue first.

### Translations
- When you add or change a translatable source string (`$l->t()` / `p($l->t())` in `templates/`, or `t()` / `n()` in `js/`), you **must** add the matching entries to every `l10n/<lang>.js` and `l10n/<lang>.json` file.
- Keep each language's `.js` and `.json` pair in sync, and preserve each file's existing `pluralForm`; plural strings need one array element per `nplurals`.
- Translations are maintained in-repo (no Transifex); include them in the same PR as the source-string change.

### Git Workflow
- **Rebase policy**: Always rebase; never create merge commits. Use `git pull --rebase` and `git rebase` before pushing.
- **Signed commits**: All commits **must** be PGP/GPG signed (`git commit -S -s`).
Expand Down