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

Gerrrr pushed a change to branch pydantic-and-split-persistence-report-json
in repository https://gitbox.apache.org/repos/asf/otava.git


    omit 4579c54  Address JSON serialization review
    omit b0761a0  Convert analysis options to Pydantic
    omit ec3ca17  Test analyzed series JSON round trip through stdlib
    omit 31886b0  Split persistence and report JSON serialization
     add 47254d9  Update Docker actions allowed by ASF CI (#172)
     add a4f5b97  Split persistence and report JSON serialization
     add 9771aa8  Test analyzed series JSON round trip through stdlib
     add 0a0d1fa  Convert analysis options to Pydantic
     add 21edff8  Address JSON serialization review

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   (4579c54)
            \
             N -- N -- N   
refs/heads/pydantic-and-split-persistence-report-json (21edff8)

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:
 .github/workflows/python-app.yml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Reply via email to