This is an automated email from the ASF dual-hosted git repository.
guan404ming pushed a change to branch backport-d9b363c-v3-3-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 337516be7f0 [v3-3-test] UI: Fix inconsistent padding between Dag Runs
and Task Instances list views (#68689) (cherry picked from commit
d9b363c630ef3e658f71bb1f2506ae53e612286a)
add 75d69a2ac77 [v3-3-test] Add wait policy examples to asset partition
example (#68658) (#68691)
add d5c1a2274a6 [v3-3-test] Fix the gap of Taiwanese Mandarin translation
(#68668) (#68695)
add 13ee8cf54ef [v3-3-test] UI: Fix inconsistent padding between Dag Runs
and Task Instances list views (#68689) (cherry picked from commit
d9b363c630ef3e658f71bb1f2506ae53e612286a)
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (337516be7f0)
\
N -- N -- N refs/heads/backport-d9b363c-v3-3-test (13ee8cf54ef)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../example_dags/example_asset_partition.py | 84 ++++++++++++++++++++++
.../ui/public/i18n/locales/zh-TW/common.json | 5 +-
.../ui/public/i18n/locales/zh-TW/dashboard.json | 12 ++++
.../airflow/ui/public/i18n/locales/zh-TW/hitl.json | 14 ++++
4 files changed, 114 insertions(+), 1 deletion(-)
