This is an automated email from the ASF dual-hosted git repository.

kaxilnaik pushed a change to branch v3-0-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


 discard 6d84c93aa80 Add `common-messaging` in the prod image
 discard 15ac9fc85d5 Refresh breeze documentation hashes in v3-0-test
 discard 7e466627a0c Update RELEASE_NOTES.rst
 discard fb13827b82f Update Airflow version to 3.0.0
 discard 9d4c7f77495 Update default branches for 3-0
     add 18c99df9541 Add ORC support to GCSToBigQueryOperator and test for 
external tables (#49188)
     add 405ca32ff2a Add `common-messaging` in the prod image (#49249)
     new 138a07805eb Update default branches for 3-0
     new a96cb54e745 Update Airflow version to 3.0.0
     new bd92283276d Update RELEASE_NOTES.rst
     new 8a6f667ac0b Refresh breeze documentation hashes in `v3-0-test`

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   (6d84c93aa80)
            \
             N -- N -- N   refs/heads/v3-0-test (8a6f667ac0b)

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.

The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../google/cloud/transfers/gcs_to_bigquery.py      |  2 +
 .../google/cloud/transfers/test_gcs_to_bigquery.py | 44 ++++++++++++++++++++++
 2 files changed, 46 insertions(+)

Reply via email to