-
Notifications
You must be signed in to change notification settings - Fork 15.2k
Move Dag, run and TI into common.json #51622
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also makes very much sense to me! Go for it!
7326aa3
to
847e8c2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes me realize how incomplete some translations are. I really hope people take a look at this in advance of 3.1.0
@pierrejeambrun Yeah, if we don't see progress on a language at least 2 weeks before we plan to release 3.1.0 then I think we should comment it out. I only want to release languages with full support |
* Move Dag, run and TI into common.json * Update more translation refs * Consolidate a few more fields, fix german keys * Extra consolidation plus refactor keys for all other languages * Fix config
* Move Dag, run and TI into common.json * Update more translation refs * Consolidate a few more fields, fix german keys * Extra consolidation plus refactor keys for all other languages * Fix config
Clean up redundancies in our translation files:
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in airflow-core/newsfragments.