(sling-org-apache-sling-committer-cli) branch feature/SLING-13253-site-shallow-clone updated (89cf373 -> 2558409)

[ro...@apache.org]

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

royteeuwen pushed a change to branch feature/SLING-13253-site-shallow-clone
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-committer-cli.git


 discard 89cf373  SLING-13253 - update-local-site: cover the git flow with real JGit
 discard 168e92d  SLING-13253 - update-local-site: shallow-clone the site checkout
 discard b02081d  SLING-13253 - update-local-site: drop the superseded name-based matching
 discard 858e5f1  SLING-13253 - finalize: update the Sling website as the last step
     add 2fec9b7  SLING-13253 - finalize: update the Sling website as the last step
     add a0b8671  SLING-13253 - update-local-site: drop the superseded name-based matching
     add db18a62  SLING-13253 - update-local-site: shallow-clone the site checkout
     add 2558409  SLING-13253 - update-local-site: cover the git flow with real JGit

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   (89cf373)
            \
             N -- N -- N   refs/heads/feature/SLING-13253-site-shallow-clone (2558409)

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: