potiuk opened a new pull request, #63307:
URL: https://github.com/apache/airflow/pull/63307

   …coverage, unused) (#62983)
   
   * Improve translation completeness checker: required keys, coverage, unused
   
   - Required keys: EN base + plural forms for locale when EN has {{count}}
   - Merge Extra and Unused into single Unused (keys not required)
   - Table: Required (base EN), Required (plural), Total required, Translated, 
Missing, Coverage (translated/total), TODOs, Unused
   - Coverage uses only real translations (exclude TODO placeholders)
   - Rename --remove-extra to --remove-unused; remove_unused_translations()
   - Update docs, SKILL, README, and help SVG
   
   * Add translation:pt-BR section to boring-cyborg config
   
   * Revert "Add translation:pt-BR section to boring-cyborg config"
   
   This reverts commit dda93a9ef391741157ce150d2bf2d1256da198d6.
   
   * Apply ruff format to ui_commands.py
   
   * Update breeze docs: regenerate check-translation-completeness output
   
   * Update ui_commands.py
   
   
   
   * fix(breeze): translation checker row style (red for missing keys)
   
   Fix unreachable red branch in style logic: use red for missing keys, yellow 
for todos/unused, bold green when all clear. Also remove unused missing_counts 
param and rename extra_keys to unused_keys.
   
   ---------
   (cherry picked from commit 69257f04ee0d62e6e3a25996fb24d033143cc7df)
   
    <!-- SPDX-License-Identifier: Apache-2.0
         https://www.apache.org/licenses/LICENSE-2.0 -->
   
   <!--
   Thank you for contributing!
   
   Please provide above a brief description of the changes made in this pull 
request.
   Write a good git commit message following this guide: 
http://chris.beams.io/posts/git-commit/
   
   Please make sure that your code changes are covered with tests.
   And in case of new features or big changes remember to adjust the 
documentation.
   
   Feel free to ping (in general) for the review if you do not see reaction for 
a few days
   (72 Hours is the minimum reaction time you can expect from volunteers) - we 
sometimes miss notifications.
   
   In case of an existing issue, reference it using one of the following:
   
   * closes: #ISSUE
   * related: #ISSUE
   -->
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   <!--
   If generative AI tooling has been used in the process of authoring this PR, 
please
   change below checkbox to `[X]` followed by the name of the tool, uncomment 
the "Generated-by".
   -->
   
   - [ ] Yes (please specify the tool below)
   
   <!--
   Generated-by: [Tool Name] following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   -->
   
   ---
   
   * Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information. Note: commit author/co-author name and email in commits 
become permanently public when merged.
   * For fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   * When adding dependency, check compliance with the [ASF 3rd Party License 
Policy](https://www.apache.org/legal/resolved.html#category-x).
   * For significant user-facing changes create newsfragment: 
`{pr_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
 You can add this file in a follow-up commit after the PR is created so you 
know the PR number.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to