This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/2.26.x/maven-patch-updates-a4a2f91a45
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
omit ca91fb50ee Bump the maven-patch-updates group across 1 directory with
33 updates
add b2a3c281f5 Change `build` and `codeql-analysis` triggers
add 913534f51c Add Dependabot `analyze` and `process` workflows
add 2edd3fc1a9 Restore default permissions
add b37a59451e Bump the maven-patch-updates group across 1 directory with
33 updates
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 (ca91fb50ee)
\
N -- N -- N
refs/heads/dependabot/maven/2.26.x/maven-patch-updates-a4a2f91a45 (b37a59451e)
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:
...odeql-analysis.yaml => analyze-dependabot.yaml} | 31 +++++++---------
.github/workflows/build.yaml | 15 +++++---
.github/workflows/codeql-analysis.yaml | 16 +++++++--
...odeql-analysis.yaml => process-dependabot.yaml} | 42 ++++++++++++----------
4 files changed, 61 insertions(+), 43 deletions(-)
copy .github/workflows/{codeql-analysis.yaml => analyze-dependabot.yaml} (57%)
copy .github/workflows/{codeql-analysis.yaml => process-dependabot.yaml} (50%)
