This is an automated email from the ASF dual-hosted git repository.
kwin pushed a change to branch feature/requireDependencyScope
in repository https://gitbox.apache.org/repos/asf/sling-maven-enforcer-rules.git
discard ba6520f Rule to enforce that all dependencies have an explicitly set
scope
add fb15f24 SLING-11410 Rule to enforce that all dependencies have an
explicitly set scope
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 (ba6520f)
\
N -- N -- N refs/heads/feature/requireDependencyScope (fb15f24)
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:
