fix(i18n): Translate trigger as 觸發器, triggerer as 觸發者 and dagRun.triggeredBy as 觸發來源#58988
Merged
Lee-W merged 1 commit intoapache:mainfrom Dec 3, 2025
Merged
Conversation
jason810496
approved these changes
Dec 3, 2025
Member
jason810496
left a comment
There was a problem hiding this comment.
Yeah, 觸發者 is much more accurate than 觸發器 as Triggerer.
Thanks for the improvement!
github-actions bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Dec 3, 2025
… dagRun.triggeredBy as 觸發來源 (apache#58988) (cherry picked from commit dcc88f1) Co-authored-by: Wei Lee <weilee.rx@gmail.com>
itayweb
pushed a commit
to itayweb/airflow
that referenced
this pull request
Dec 6, 2025
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.
Why
Both trigger and triggerer were translated as 觸發器. We need a way to distinguish it.
What
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.