feat: update translations via @LingoDotDev#24301
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
|
Lingo.dev seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
WalkthroughThis PR adds two new localization keys, webhook_organizer_username and webhook_organizer_username_in_org, to multiple locale files under apps/web/public/static/locales//common.json (including ar, az, bg, bn, ca, cs, da, de, el, es-419, es, et, eu, fi, fr, he, hu, it, ja, km, ko, nl, no, pl, pt-BR, pt, ro, ru, sk-SK, sr, sv, tr, uk, vi, zh-CN, zh-TW). These keys sit alongside existing webhook_organizer_ entries (e.g., locale/timezone). No other files or logic are modified. Possibly related PRs
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
apps/web/public/static/locales/he/common.json (1)
3680-3681: Align with existing gender-inclusive phrasing.Neighbor strings (e.g., Lines 3676‑3678) use “המארגן/ת”. These new translations revert to masculine-only wording, creating an inconsistent voice. Please update to something like:
-"webhook_organizer_username": "שם המשתמש של המארגן (לדוגמה, 'john.doe')", -"webhook_organizer_username_in_org": "שם המשתמש של המארגן בארגון שלהם (לדוגמה, 'john.doe')", +"webhook_organizer_username": "שם המשתמש של המארגן/ת (לדוגמה, 'john.doe')", +"webhook_organizer_username_in_org": "שם המשתמש של המארגן/ת בארגון שלו/ה (לדוגמה, 'john.doe')",
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
i18n.lockis excluded by!**/*.lock
📒 Files selected for processing (36)
apps/web/public/static/locales/ar/common.json(1 hunks)apps/web/public/static/locales/az/common.json(1 hunks)apps/web/public/static/locales/bg/common.json(1 hunks)apps/web/public/static/locales/bn/common.json(1 hunks)apps/web/public/static/locales/ca/common.json(1 hunks)apps/web/public/static/locales/cs/common.json(1 hunks)apps/web/public/static/locales/da/common.json(1 hunks)apps/web/public/static/locales/de/common.json(1 hunks)apps/web/public/static/locales/el/common.json(1 hunks)apps/web/public/static/locales/es-419/common.json(1 hunks)apps/web/public/static/locales/es/common.json(1 hunks)apps/web/public/static/locales/et/common.json(1 hunks)apps/web/public/static/locales/eu/common.json(1 hunks)apps/web/public/static/locales/fi/common.json(1 hunks)apps/web/public/static/locales/fr/common.json(1 hunks)apps/web/public/static/locales/he/common.json(1 hunks)apps/web/public/static/locales/hu/common.json(1 hunks)apps/web/public/static/locales/it/common.json(1 hunks)apps/web/public/static/locales/ja/common.json(1 hunks)apps/web/public/static/locales/km/common.json(1 hunks)apps/web/public/static/locales/ko/common.json(1 hunks)apps/web/public/static/locales/nl/common.json(1 hunks)apps/web/public/static/locales/no/common.json(1 hunks)apps/web/public/static/locales/pl/common.json(1 hunks)apps/web/public/static/locales/pt-BR/common.json(1 hunks)apps/web/public/static/locales/pt/common.json(1 hunks)apps/web/public/static/locales/ro/common.json(1 hunks)apps/web/public/static/locales/ru/common.json(1 hunks)apps/web/public/static/locales/sk-SK/common.json(1 hunks)apps/web/public/static/locales/sr/common.json(1 hunks)apps/web/public/static/locales/sv/common.json(1 hunks)apps/web/public/static/locales/tr/common.json(1 hunks)apps/web/public/static/locales/uk/common.json(1 hunks)apps/web/public/static/locales/vi/common.json(1 hunks)apps/web/public/static/locales/zh-CN/common.json(1 hunks)apps/web/public/static/locales/zh-TW/common.json(1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: bandhan-majumder
PR: calcom/cal.com#23192
File: packages/features/insights/components/booking/LeastCompletedBookings.tsx:31-31
Timestamp: 2025-08-21T05:55:35.187Z
Learning: Cal.com uses an automated i18n system with lingo.dev that automatically propagates new translation keys from en/common.json to all other locale files and creates PRs with proper translations. The system includes a check-missing-translations.ts script that adds English placeholders for missing keys, and a GitHub workflow that triggers lingo.dev automation to translate and create PRs.
🔇 Additional comments (8)
apps/web/public/static/locales/fr/common.json (1)
3680-3681: Translations look good.New webhook organizer username strings read naturally in French and match the English intent.
apps/web/public/static/locales/km/common.json (1)
3680-3681: Translations look consistent.The new webhook organizer username strings follow the existing pattern and read well next to the surrounding locale entries.
apps/web/public/static/locales/ca/common.json (1)
3680-3681: Localization entries look accurateLes noves cadenes segueixen el patró existent i la traducció catalana és coherent amb la resta del fitxer.
apps/web/public/static/locales/bn/common.json (1)
3680-3681: New keys translated correctlyStrings align with the newly introduced webhook organizer username keys and preserve the expected examples. Looks good.
apps/web/public/static/locales/sk-SK/common.json (1)
3680-3681: Slovak translations look solid.Terminology and examples align with existing webhook organiser strings. Good addition.
apps/web/public/static/locales/ru/common.json (1)
3680-3681: Translations look consistent — New organizer username strings align with surrounding webhook entries and maintain established phrasing.apps/web/public/static/locales/az/common.json (1)
3680-3681: Translations aligned with new webhook username keys.Both additions mirror the expected English phrasing, include the sample username context, and stay consistent with surrounding localization patterns. LGTM.
apps/web/public/static/locales/nl/common.json (1)
3680-3681: Dutch translations look solidNieuwe sleutelvertalingen sluiten goed aan bij de bestaande webhook-variabelen en behouden voorbeeldnotatie.
| "webhook_organizer_username": "Nome de usuário do organizador (ex.: 'john.doe')", | ||
| "webhook_organizer_username_in_org": "Nome de usuário do organizador na organização (ex.: 'john.doe')", |
There was a problem hiding this comment.
Fix Portuguese locale wording
Para manter a consistência com o pt-PT existente (ver p.ex. Line 298 “Nome de utilizador”), estas novas entradas devem usar “utilizador” e não “usuário”.
- "webhook_organizer_username": "Nome de usuário do organizador (ex.: 'john.doe')",
- "webhook_organizer_username_in_org": "Nome de usuário do organizador na organização (ex.: 'john.doe')",
+ "webhook_organizer_username": "Nome de utilizador do organizador (ex.: 'john.doe')",
+ "webhook_organizer_username_in_org": "Nome de utilizador do organizador na organização (ex.: 'john.doe')",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "webhook_organizer_username": "Nome de usuário do organizador (ex.: 'john.doe')", | |
| "webhook_organizer_username_in_org": "Nome de usuário do organizador na organização (ex.: 'john.doe')", | |
| "webhook_organizer_username": "Nome de utilizador do organizador (ex.: 'john.doe')", | |
| "webhook_organizer_username_in_org": "Nome de utilizador do organizador na organização (ex.: 'john.doe')", |
🤖 Prompt for AI Agents
In apps/web/public/static/locales/pt/common.json around lines 3680-3681, the two
new Portuguese strings use "usuário" but the pt locale uses "utilizador"; update
both values to replace "usuário" with "utilizador" so they read "Nome de
utilizador do organizador (ex.: 'john.doe')" and "Nome de utilizador do
organizador na organização (ex.: 'john.doe')".
| "webhook_organizer_username": "Organisatörens användarnamn (t.ex. 'john.doe')", | ||
| "webhook_organizer_username_in_org": "Organisatörens användarnamn i deras organisation (t.ex. 'john.doe')", |
There was a problem hiding this comment.
Harmonize organizer terminology in Swedish.
Neighboring webhook organizer strings use “Arrangörens …”, but these new entries switch to “Organisatörens …”. Please align the wording (e.g. “Arrangörens användarnamn …”) so the UI stays consistent.
🤖 Prompt for AI Agents
In apps/web/public/static/locales/sv/common.json around lines 3680 to 3681, the
two webhook organizer strings use "Organisatörens" while neighboring keys use
"Arrangörens"; update both values to use "Arrangörens" (e.g. "Arrangörens
användarnamn (t.ex. 'john.doe')" and "Arrangörens användarnamn i deras
organisation (t.ex. 'john.doe')") so the Swedish terminology is consistent
across the UI.
| "webhook_organizer_username": "組織者的使用者名稱（例如：'john.doe'）", | ||
| "webhook_organizer_username_in_org": "組織內部組織者的使用者名稱（例如：'john.doe'）", |
There was a problem hiding this comment.
Align with existing zh-TW terminology.
Other webhook_organizer_* strings in this locale consistently use「主辦者」for “organizer” (e.g., webhook_organizer_email). These two new keys switch to「組織者」, which breaks glossary consistency. Please update both values to stick with「主辦者」so the UI terminology stays uniform.
- "webhook_organizer_username": "組織者的使用者名稱（例如：'john.doe'）",
- "webhook_organizer_username_in_org": "組織內部組織者的使用者名稱（例如：'john.doe'）",
+ "webhook_organizer_username": "主辦者的使用者名稱（例如：「john.doe」）",
+ "webhook_organizer_username_in_org": "組織內部主辦者的使用者名稱（例如：「john.doe」）",🤖 Prompt for AI Agents
In apps/web/public/static/locales/zh-TW/common.json around lines 3680-3681, the
two new keys use 「組織者」instead of the established 「主辦者」 term; update the values
for "webhook_organizer_username" and "webhook_organizer_username_in_org" to
replace 「組織者」with 「主辦者」 so they match the existing zh-TW glossary and remain
consistent with other keys like webhook_organizer_email.
3 participants
Hey team,
Lingo.dev here with fresh translations!
In this update
Next Steps