This is an automated email from the ASF dual-hosted git repository.
lprimak pushed a change to branch main
in repository https://gitbox.apache.org/repos/asf/shiro.git
omit a0af4ef9e chore(dependabot): don't update checkstyle for 2.x
omit 7d4829cbf *** TEMPORARY *** disable main branch protection
omit efd594d9a chore(asf.yaml): don't dismiss stale reviews
omit 90288b44a * chore(asf.yaml): correct merge buttons are now enabled
(squash, rebase) and merge
new 4207abc95 chore(asf.yaml): correct merge buttons are now enabled
(squash, rebase) and merge chore(dependabot): don't update major version of
checkstyle in 2.x
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 (a0af4ef9e)
\
N -- N -- N refs/heads/main (4207abc95)
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 1 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:
.asf.yaml | 1 +
1 file changed, 1 insertion(+)
