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

maximebeauchemin pushed a change to branch trigger_ci
in repository https://gitbox.apache.org/repos/asf/superset.git


 discard 6f96108974 creating groups for docker and docs
 discard b16e59d1ae down
 discard 3b986941fb print python version
 discard 1027fbad78 print python version
 discard 453f950255 more output
 discard 29ea5a4d6c commits
 discard d1f320e3d7 mv
 discard bd0e2168e7 rm extra step
 discard 122a46db24 rm extra step
 discard d959cd25da typo
 discard f56ca414f4 remove dependency on no-op
 discard a76e189ae0 leave superset-python-integrationtest untouched
 discard 49ac6a79f9 touch superset/
 discard f845b9dc96 fix: add more path triggers for python GHAs
     add d20555aa71 fix: add more path triggers for python GHAs

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   (6f96108974)
            \
             N -- N -- N   refs/heads/trigger_ci (d20555aa71)

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:
 scripts/change_detector.py | 64 ++++++++++++++++++++--------------------------
 1 file changed, 28 insertions(+), 36 deletions(-)

Reply via email to