This is an automated email from the ASF dual-hosted git repository.
olamy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-surefire.git
The following commit(s) were added to refs/heads/master by this push:
new f37a0e7fa no more Jira in pr template (#854)
f37a0e7fa is described below
commit f37a0e7fa9758d11dd1f0521c4dd33c5e5199354
Author: Olivier Lamy <ol...@apache.org>
AuthorDate: Sat May 31 09:15:30 2025 +1000
no more Jira in pr template (#854)
Signed-off-by: Olivier Lamy <ol...@apache.org>
---
.github/pull_request_template.md | 8 --------
1 file changed, 8 deletions(-)
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 16f209adf..1c57fd008 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,15 +1,7 @@
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/SUREFIRE) 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 `[SUREFIRE-XXX] - Fixes bug in
ApproximateQuantiles`,
- where you replace `SUREFIRE-XXX` 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 install` to make sure basic checks pass. A more thorough
check will
be performed on your pull request automatically.
