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

amaannawab923 pushed a change to branch asset-demo
in repository https://gitbox.apache.org/repos/asf/superset.git


 discard 14976c59544 fix(asset-approval): make the seed produce the state it 
describes
 discard 2a3042d8bec feat(asset-approval): seed the demo's cast instead of 
maker/checker/viewer
 discard 0c0e6a634fd docs(asset-approval): give QA the whole happy flow, with 
every account
     new 0600d4b1fca docs(asset-approval): give QA the whole happy flow, with 
every account
     new 8950441224e feat(asset-approval): seed the demo's cast instead of 
maker/checker/viewer
     new 5b8532c2845 fix(asset-approval): make the seed produce the state it 
describes

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   (14976c59544)
            \
             N -- N -- N   refs/heads/asset-demo (5b8532c2845)

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 3 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:

Reply via email to