This is an automated email from the ASF dual-hosted git repository.
michaelo pushed a change to branch doxia-2.0.0
in repository https://gitbox.apache.org/repos/asf/maven-checkstyle-plugin.git
discard b227537 [MCHECKSTYLE-446] Dynamically calculate
xrefLocation/xrefTestLocation
discard 41ad40a [MCHECKSTYLE-445] Upgrade to Doxia 2.0.0 Milestone Stack
discard 46103d8 Bump master to 4.0.0-M1-SNAPSHOT
add a29a294 Bump maven-gh-actions-shared to v4
new d5d15de Bump master to 4.0.0-M1-SNAPSHOT
new d86043e [MCHECKSTYLE-445] Upgrade to Doxia 2.0.0 Milestone Stack
new de27774 [MCHECKSTYLE-446] Dynamically calculate
xrefLocation/xrefTestLocation
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 (b227537)
\
N -- N -- N refs/heads/doxia-2.0.0 (de27774)
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:
.github/workflows/maven-verify.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
