Repository navigation
Conversation
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummarySingle-line Uzbek catalog casing fix ( Files Reviewed (1 file)
Previous Review Summary (commit 46a9352)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 46a9352)Status: No Issues Found | Recommendation: Merge Executive SummarySingle-line Uzbek catalog casing correction ( Files Reviewed (1 file)
Reviewed by deepseek-v4.1-flash · Input: 0 · Output: 0 · Cached: 0 Review guidance: REVIEW.md from base branch |
pandemicsyn
approved these changes
Sep 29, 2026
iscekic
force-pushed
the
kwf/janitor-mobile-pr-review-761e9d58b4
branch
from
September 30, 2026 03:34
46a9352 to
bae4e6e
Compare
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.
Changelog for users
Changelog for maintainers
E2E proof
Published PR head:
bae4e6ed1176c90646f0b54a502e54402cea0e24(same tree as proved sourcee4509e3078a70c6730ef550a2a98fda448778b77).common.pullRequest holds the malformed form "pR" instead of the accepted term "PR"; it is interpolated as the mid-sentence {{term}} in PR Review sentences, so users read e.g. "bu pR", unlike the correctly cased PR used in uz's prReview strings.
Code trace:
apps/mobile/src/i18n/locales/uz.json:39 changed in e4509e3078a70c6730ef550a2a98fda448778b77. Sense check (model): uz.json:39 changes "pullRequest": "pR" to "PR", directly fixing the malformed term the claim describesChanged lines
Asserted value:
uz PR term toast: PRni ochib bo'lmadi.. Sense check (model): Base log shows TextView "pRni ochib bo'lmadi." (ui-assert exited 1); head log shows TextView "PRni ochib bo'lmadi." and asserts "uz PR term toast: PRni ochib bo'lmadi.", matching the base screenshot toast "pRni ochib bo'lmadi." and head screenshot toast "PRni ochib bo'lmadi."ecac00c2faacbae4e6ed1176After drive: the Uzbek session screen for the seeded session: the header shows the 'ochiq PR #7' badge and the body shows the session load error 'Bu sessiyani yuklab bo'lmadi.', with the open-PR error toast at the bottom reading 'PRni ochib bo'lmadi.' on the head revision (the base revision reads 'pRni ochib bo'lmadi.')
Base log: ui-assert a3e00bee1c8f exited 1
Head log: ui-assert a3e00bee1c8f exited 0
Owner request