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

   Supersedes #76451.
   
   The generated backport carried the translation commit across unchanged, so 
it brought 15 keys whose English strings only exist on `main` and are never 
looked up on this branch. `breeze ui check-translation-completeness --language 
it` reports every one of them under "Unused keys":
   
   ```
   browse:     dagBundles.files.importErrorForbidden
   common:     error.reload, pagination.nextPage, pagination.previousPage,
               search.advanced.toggleLabel,
               shortcuts.descriptions.selectGridCellRange,
               shortcuts.descriptions.toggleGridCellSelection
   components: backfill.completed, backfill.running, backfill.status,
               flexibleForm.validationErrorArrayElement
   dag:        logs.search.nextMatch, logs.search.previousMatch
   dags:       filters.hasImportErrors
   hitl:       response.selectAtLeastOne
   ```
   
   This branch is the same backport with those keys dropped, via `breeze ui 
check-translation-completeness --language it --remove-unused`. No translated 
value is changed and no key is added; the Italian work and its authorship are 
untouched.
   
   Note that CI cannot catch this today — `.github/workflows/basic-tests.yml` 
runs the check as `breeze ui check-translation-completeness || true`, so unused 
keys never fail the build. #76451 is green despite carrying all 15. Worth 
tightening separately, once the locales that would go red are cleaned up.
   
   related: #76411
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes - Claude Code (Opus 5)
   
   Generated-by: Claude Code (Opus 5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)


-- 
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