Skip to content
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.

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

Update l10n for 1.37.x (Chromium 100) (uplift to 1.37.x). #12822

Merged
merged 2 commits into from
Mar 30, 2022

Conversation

mkarolin
Copy link
Collaborator

Fixes brave/brave-browser#21963
Uplift from #12818

Submitter Checklist:

  • I confirm that no security/privacy review is needed, or that I have requested one
  • There is a ticket for my issue
  • Used Github auto-closing keywords in the PR description above
  • Wrote a good PR/commit description
  • Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
  • Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
  • Checked the PR locally: npm run test -- brave_browser_tests, npm run test -- brave_unit_tests, npm run lint, npm run gn_check, npm run tslint
  • Ran git rebase master (if needed)

Reviewer Checklist:

  • A security review is not needed, or a link to one is included in the PR description
  • New files have MPL-2.0 license header
  • Adequate test coverage exists to prevent regressions
  • Major classes, functions and non-trivial code blocks are well-commented
  • Changes in component dependencies are properly reflected in gn
  • Code follows the style guide
  • Test plan is specified in PR before merging

After-merge Checklist:

Test Plan:

Update l10n for 1.37.x (Chromium 100)
@mkarolin mkarolin requested a review from a team March 30, 2022 00:06
@mkarolin mkarolin requested a review from a team as a code owner March 30, 2022 00:06
@mkarolin mkarolin requested review from bsclifton and removed request for a team March 30, 2022 00:06
@mkarolin mkarolin self-assigned this Mar 30, 2022
@mkarolin mkarolin requested a review from deeppandya March 30, 2022 00:06
@mkarolin mkarolin force-pushed the maxk-1.37.x-l10n-1.37.x branch from ebf6b2b to 6ed4b5a Compare March 30, 2022 01:25
@mkarolin mkarolin added this to the 1.37.x - Release milestone Mar 30, 2022
Copy link
Member

@kjozwiak kjozwiak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Uplift into 1.37.x approved 👍

@kjozwiak kjozwiak merged commit 6a5fe70 into 1.37.x Mar 30, 2022
@kjozwiak kjozwiak deleted the maxk-1.37.x-l10n-1.37.x branch March 30, 2022 03:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants