Repository navigation
Fix small pt-BR translation errors - #549
Open
yurineves92 wants to merge 2 commits into
Open
yurineves92 wants to merge 2 commits into
yurineves92 wants to merge 2 commits into
Conversation
Restore lists that po4a flattened into a single paragraph in the Docker Swarm, Sentry and asset pages. Add the pt-BR label to the report issue link. Align the menu, tables of contents and link text with page titles, and use "POO" and "Ser explícito" consistently.
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis PR fixes pt-BR documentation presentation and terminology by repairing flattened PO translation lists, aligning translated navigation and link text with page titles, and adding the missing localized Report Issue label. Translation changes remain in .po files and depend on the existing Update translations workflow for generated sources. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've found 1 issue
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="src/.vitepress/config.js" line_range="1449" />
<code_context>
items: [
{text: 'Visão geral de testes', link: '/pt-BR/guide/testing/overview'},
- {text: 'Configurando o ambiente de testes', link: '/pt-BR/guide/testing/environment-setup'},
+ {text: 'Configuração do ambiente de testes', link: '/pt-BR/guide/testing/environment-setup'},
{text: 'Testes unitários', link: '/pt-BR/guide/testing/unit'},
{text: 'Testes funcionais', link: '/pt-BR/guide/testing/functional'},
</code_context>
<issue_to_address>
**Changes exceed permitted paths**
When this PR includes the shown changes, the navigation edits and issue-report label change are outside the permitted documentation directories, so this PR violates the repository’s edit-scope rule.
Keep edits within `src/cookbook`, `src/guide`, and `src/internals`, or update the repository rule to permit these paths.
Also at `src/.vitepress/theme/components/ReportIssue.vue:24`.
</issue_to_address>Sourcery assessment
Approval pending. 1 finding to address first.
Blocking findings: src/.vitepress/config.js:1449
| items: [ | ||
| {text: 'Visão geral de testes', link: '/pt-BR/guide/testing/overview'}, | ||
| {text: 'Configurando o ambiente de testes', link: '/pt-BR/guide/testing/environment-setup'}, | ||
| {text: 'Configuração do ambiente de testes', link: '/pt-BR/guide/testing/environment-setup'}, |
There was a problem hiding this comment.
🟡 Medium · Changes exceed permitted paths
When this PR includes the shown changes, the navigation edits and issue-report label change are outside the permitted documentation directories, so this PR violates the repository’s edit-scope rule.
Keep edits within src/cookbook, src/guide, and src/internals, or update the repository rule to permit these paths.
Also at src/.vitepress/theme/components/ReportIssue.vue:24.
Prompt for AI agents
In `src/.vitepress/config.js` at line 1449:
**Changes exceed permitted paths**
When this PR includes the shown changes, the navigation edits and issue-report label change are outside the permitted documentation directories, so this PR violates the repository’s edit-scope rule.
Keep edits within `src/cookbook`, `src/guide`, and `src/internals`, or update the repository rule to permit these paths.
Also at `src/.vitepress/theme/components/ReportIssue.vue:24`.From .github/copilot-instructions.md L22:
- Edits are permitted only in `src/cookbook`, `src/guide` and `src/internals`.Run po4a so src/pt-BR matches the updated .po files. The Update translations workflow cannot push to a fork branch, so the generated files need to be part of the pull request.
This branch has not been deployed
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
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.
Small follow-up to #546 with fixes found while reviewing the published Brazilian Portuguese docs.
Changes
msgstr, the same way the Russian Sentry translation does it.pt-BRlabel inReportIssue.vue, which fell back to English.Notes
.pofiles.src/pt-BRwas regenerated with theghcr.io/yiisoft-contrib/po4a:0.74image, because theUpdate translationsworkflow cannot push to a fork branch.npm run buildwas not run locally.guide/security/overview.mdlinks toviews/view.md#security, and that section does not exist in English either. This PR does not change it.Summary by Sourcery
Correct Brazilian Portuguese documentation formatting, navigation labels, terminology, and issue-reporting localization.
Bug Fixes:
Enhancements:
Documentation: