This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/commons-io-commons-io-2.14.0
in repository
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-scripting-sightly-repl.git
discard 9aa1839 Bump commons-io:commons-io from 2.4 to 2.14.0
add 40a783d SLING-12459 - Redirect sonarcloud notifications to
[email protected]
add 59741d7 SLING-12730 Update to Parent 62
add 2dc8b1a SLING-12730 apply spotless formatting
add bcdf3ea SLING-12730 ignore spotless code reformatting commit in git
blame
add 55ac7e9 Bump commons-io:commons-io from 2.4 to 2.14.0
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 (9aa1839)
\
N -- N -- N
refs/heads/dependabot/maven/commons-io-commons-io-2.14.0 (55ac7e9)
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:
.asf.yaml | 1 +
.git-blame-ignore-revs | 1 +
.sling-module.json | 5 ++
pom.xml | 94 +++++++++++-----------
.../repl/impl/REPLJavaSourceCodeServlet.java | 74 +++++++++--------
5 files changed, 96 insertions(+), 79 deletions(-)
create mode 100644 .git-blame-ignore-revs
create mode 100644 .sling-module.json
