You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(translations): use Brazilian Portuguese wording for pt auth strings - #19437
Updates a few pt authentication strings (and general:email) to the wording Brazilian Portuguese users expect:
key
before
after
authentication:loginUser
Iniciar sessão
Entrar
authentication:logoutUser
Encerrar sessão
Sair
authentication:logOut / logout
Log out / Logout
Sair
authentication:loggedOutSuccessfully
Log out efetuado com sucesso.
Você saiu com sucesso.
authentication:logoutSuccessful
Logout bem sucedido.
Você saiu com sucesso.
authentication:loggedIn / loginWithAnotherUser
…você deve fazer o <0>log out</0> antes.
Para entrar como outro usuário, você deve <0>sair</0> antes.
general:email
Email
E-mail
Why?
The rest of pt.ts already uses Brazilian vocabulary (usuário, arquivo, salvar, excluir, tela). These strings were the outliers: two use European Portuguese phrasing ("Iniciar/Encerrar sessão") and the others leave English words (Log out, Logout, Email) in an otherwise translated admin — which is what end users see first on the login screen and in the account menu. "Entrar"/"Sair" and "E-mail" are the standard terms in Brazilian UIs.
How?
String-only change in packages/translations/src/languages/pt.ts: no keys added or removed, <0>…</0> placeholders preserved, no changes to dateFNSKey. Does not overlap with #19430 (validation messages).
Found while setting up the admin in Portuguese for two Brazilian NGO/real-estate sites migrated from WordPress.
No actionable comments were generated in the recent review.
Walkthrough
Portuguese authentication translations now use “sair” wording for login and logout prompts and labels. The general email label changes from “Email” to “E-mail”.
The Portuguese labels are updated without an identified merge-blocking issue.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title clearly describes the Brazilian Portuguese authentication translation changes.
Description check
The description accurately covers the authentication and email translation changes.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 1 files.
Finishing Touches
Generate unit tests (beta)
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Tip
🎯 Customize your risk assessments
Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.
✅ Automatic approvals, with your rules
Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.
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.
Reviewing files that changed from the base of the PR and between 25dfb24 and 0f803a4.
Files selected for processing: 1
packages/translations/src/languages/pt.ts
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.
This branch has not been deployed
No deployments
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
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.
What?
Updates a few
ptauthentication strings (andgeneral:email) to the wording Brazilian Portuguese users expect:authentication:loginUserauthentication:logoutUserauthentication:logOut/logoutauthentication:loggedOutSuccessfullyauthentication:logoutSuccessfulauthentication:loggedIn/loginWithAnotherUser<0>log out</0>antes.<0>sair</0>antes.general:emailWhy?
The rest of
pt.tsalready uses Brazilian vocabulary (usuário, arquivo, salvar, excluir, tela). These strings were the outliers: two use European Portuguese phrasing ("Iniciar/Encerrar sessão") and the others leave English words (Log out, Logout, Email) in an otherwise translated admin — which is what end users see first on the login screen and in the account menu. "Entrar"/"Sair" and "E-mail" are the standard terms in Brazilian UIs.How?
String-only change in
packages/translations/src/languages/pt.ts: no keys added or removed,<0>…</0>placeholders preserved, no changes todateFNSKey. Does not overlap with #19430 (validation messages).Found while setting up the admin in Portuguese for two Brazilian NGO/real-estate sites migrated from WordPress.