This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.codehaus.plexus-plexus-java-1.5.0
in repository https://gitbox.apache.org/repos/asf/maven-jmod-plugin.git
omit 6c1d8af Bump org.codehaus.plexus:plexus-java from 1.0.3 to 1.5.0
add f83d4c7 Enable GitHub Issue
add ea7ae17 Update parent 44 (#42)
add f0ae4b9 Bump org.codehaus.plexus:plexus-java from 1.0.3 to 1.5.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 (6c1d8af)
\
N -- N -- N
refs/heads/dependabot/maven/org.codehaus.plexus-plexus-java-1.5.0 (f0ae4b9)
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 | 3 ++
.github/{dependabot.yml => ISSUE_TEMPLATE/BUG.yml} | 46 +++++++++++++++-------
.../{dependabot.yml => ISSUE_TEMPLATE/FEATURE.yml} | 29 ++++++++------
.../{dependabot.yml => ISSUE_TEMPLATE/config.yml} | 24 +++++------
.../{maven-verify.yml => pr-automation.yml} | 14 +++----
.github/workflows/{maven-verify.yml => stale.yml} | 13 +++---
README.md | 25 +++---------
pom.xml | 7 ++--
8 files changed, 87 insertions(+), 74 deletions(-)
copy .github/{dependabot.yml => ISSUE_TEMPLATE/BUG.yml} (54%)
copy .github/{dependabot.yml => ISSUE_TEMPLATE/FEATURE.yml} (60%)
copy .github/{dependabot.yml => ISSUE_TEMPLATE/config.yml} (62%)
copy .github/workflows/{maven-verify.yml => pr-automation.yml} (80%)
copy .github/workflows/{maven-verify.yml => stale.yml} (82%)
