This is an automated email from the ASF dual-hosted git repository.
mbuenger pushed a commit to branch maven-3.9.x
in repository https://gitbox.apache.org/repos/asf/maven.git
The following commit(s) were added to refs/heads/maven-3.9.x by this push:
new 13f6a00f53 Enable Github Issues (3.9.x)
13f6a00f53 is described below
commit 13f6a00f532f2493cb6f9d4a68adecd283854c1d
Author: Matthias Bünger <[email protected]>
AuthorDate: Fri Jun 6 16:30:23 2025 +0200
Enable Github Issues (3.9.x)
---
.github/pull_request_template.md | 28 ++++++++++++----------------
.github/workflows/release-drafter.yml | 29 +++++++++++++++++++++++++++++
README.md | 2 +-
pom.xml | 4 ++--
4 files changed, 44 insertions(+), 19 deletions(-)
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index b4a4f83334..3019d1ee26 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,18 +1,15 @@
Following this checklist to help us incorporate your
contribution quickly and easily:
- - [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MNG) filed
- for the change (usually before you start working on it). Trivial
changes like typos do not
- require a JIRA issue. Your pull request should address just this issue,
without
- pulling in other changes.
- - [ ] Each commit in the pull request should have a meaningful subject line
and body.
- - [ ] Format the pull request title like `[MNG-XXX] SUMMARY`, where you
replace `MNG-XXX`
- and `SUMMARY` with the appropriate JIRA issue. Best practice is to use
the JIRA issue
- title in the pull request title and in the first line of the commit
message.
- - [ ] Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
- - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough
check will
- be performed on your pull request automatically.
- - [ ] You have run the [Core IT][core-its] successfully.
+- [ ] Your pull request should address just one issue, without pulling in
other changes.
+- [ ] Write a pull request description that is detailed enough to understand
what the pull request does, how, and why.
+- [ ] Each commit in the pull request should have a meaningful subject line
and body.
+ Note that commits might be squashed by a maintainer on merge.
+- [ ] Write unit tests that match behavioral changes, where the tests fail if
the changes to the runtime are not applied.
+ This may not always be possible but is a best-practice.
+- [ ] Run `mvn verify` to make sure basic checks pass.
+ A more thorough check will be performed on your pull request automatically.
+- [ ] You have run the [Core IT][core-its] successfully.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
@@ -22,8 +19,7 @@ To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- - [ ] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
+- [ ] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
+- [ ] In any other case, please file an [Apache Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf).
- - [ ] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
-
-[core-its]: https://maven.apache.org/core-its/core-it-suite/
+[core-its]: https://maven.apache.org/core-its/core-it-suite/
\ No newline at end of file
diff --git a/.github/workflows/release-drafter.yml
b/.github/workflows/release-drafter.yml
new file mode 100644
index 0000000000..72e29acfc3
--- /dev/null
+++ b/.github/workflows/release-drafter.yml
@@ -0,0 +1,29 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements. See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership. The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied. See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+name: Release Drafter
+on:
+ push:
+ branches:
+ - maven-3.9.x
+ workflow_dispatch:
+
+jobs:
+ update_release_draft:
+ uses:
apache/maven-gh-actions-shared/.github/workflows/release-drafter.yml@v4
+ with:
+ config-name: 'release-drafter-3.x.yml'
\ No newline at end of file
diff --git a/README.md b/README.md
index 96f4cca81b..5418969fd6 100644
--- a/README.md
+++ b/README.md
@@ -29,7 +29,7 @@ Apache Maven is a software project management and
comprehension tool. Based on
the concept of a project object model (POM), Maven can manage a project's
build, reporting and documentation from a central piece of information.
-If you think you have found a bug, please file an issue in the [Maven Issue
Tracker](https://issues.apache.org/jira/browse/MNG).
+If you think you have found a bug, please file an issue in the [Maven Issue
Tracker](https://github.com/apache/maven/issues).
Documentation
-------------
diff --git a/pom.xml b/pom.xml
index ce22852834..1d1d7d64a3 100644
--- a/pom.xml
+++ b/pom.xml
@@ -108,8 +108,8 @@ under the License.
<url>https://github.com/apache/maven/tree/${project.scm.tag}</url>
</scm>
<issueManagement>
- <system>jira</system>
- <url>https://issues.apache.org/jira/browse/MNG</url>
+ <system>GitHub Issues</system>
+ <url>https://github.com/apache/maven/issues</url>
</issueManagement>
<ciManagement>
<system>Jenkins</system>
