Skip to content

Commit 3f47dd0

Browse files
slawekjaranowskislawekjaranowski
committed
Enable GitHub Issues
1 parent e51cef8 commit 3f47dd0

File tree

7 files changed

+133
-65
lines changed

7 files changed

+133
-65
lines changed

‎.asf.yaml

+5-1
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,12 @@ github:
3030
rebase: true
3131
autolink_jira:
3232
- MPIR
33+
del_branch_on_merge: true
34+
features:
35+
issues: true
36+
3337
notifications:
3438
commits: [email protected]
3539
issues: [email protected]
3640
pullrequests: [email protected]
37-
jira_options: link label comment
41+
jira_options: link label

‎.github/ISSUE_TEMPLATE/BUG.yml

+48
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
#
2+
# Licensed to the Apache Software Foundation (ASF) under one or more
3+
# contributor license agreements. See the NOTICE file distributed with
4+
# this work for additional information regarding copyright ownership.
5+
# The ASF licenses this file to You under the Apache License, Version 2.0
6+
# (the "License"); you may not use this file except in compliance with
7+
# the License. You may obtain a copy of the License at
8+
#
9+
# http://www.apache.org/licenses/LICENSE-2.0
10+
#
11+
# Unless required by applicable law or agreed to in writing, software
12+
# distributed under the License is distributed on an "AS IS" BASIS,
13+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14+
# See the License for the specific language governing permissions and
15+
# limitations under the License.
16+
#
17+
18+
# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
19+
20+
name: Bug Report
21+
description: File a bug report
22+
labels: ["bug"]
23+
24+
body:
25+
- type: markdown
26+
attributes:
27+
value: |
28+
Thanks for taking the time to fill out this bug report.
29+
30+
Simple fixes in single PRs do not require issues.
31+
32+
**Do you use the latest project version?**
33+
34+
- type: input
35+
id: version
36+
attributes:
37+
label: Affected version
38+
validations:
39+
required: true
40+
41+
- type: textarea
42+
id: massage
43+
attributes:
44+
label: Bug description
45+
validations:
46+
required: true
47+
48+

‎.github/ISSUE_TEMPLATE/FEATURE.yml

+35
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
#
2+
# Licensed to the Apache Software Foundation (ASF) under one or more
3+
# contributor license agreements. See the NOTICE file distributed with
4+
# this work for additional information regarding copyright ownership.
5+
# The ASF licenses this file to You under the Apache License, Version 2.0
6+
# (the "License"); you may not use this file except in compliance with
7+
# the License. You may obtain a copy of the License at
8+
#
9+
# http://www.apache.org/licenses/LICENSE-2.0
10+
#
11+
# Unless required by applicable law or agreed to in writing, software
12+
# distributed under the License is distributed on an "AS IS" BASIS,
13+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14+
# See the License for the specific language governing permissions and
15+
# limitations under the License.
16+
#
17+
18+
# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
19+
20+
name: Feature request
21+
description: File a proposal for new feature, improvement
22+
labels: ["enhancement"]
23+
24+
body:
25+
- type: markdown
26+
attributes:
27+
value: |
28+
Thanks for taking the time to fill out this new feature, improvement proposal.
29+
30+
- type: textarea
31+
id: massage
32+
attributes:
33+
label: New feature, improvement proposal
34+
validations:
35+
required: true

‎.github/ISSUE_TEMPLATE/config.yml

+30
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
#
2+
# Licensed to the Apache Software Foundation (ASF) under one or more
3+
# contributor license agreements. See the NOTICE file distributed with
4+
# this work for additional information regarding copyright ownership.
5+
# The ASF licenses this file to You under the Apache License, Version 2.0
6+
# (the "License"); you may not use this file except in compliance with
7+
# the License. You may obtain a copy of the License at
8+
#
9+
# http://www.apache.org/licenses/LICENSE-2.0
10+
#
11+
# Unless required by applicable law or agreed to in writing, software
12+
# distributed under the License is distributed on an "AS IS" BASIS,
13+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14+
# See the License for the specific language governing permissions and
15+
# limitations under the License.
16+
#
17+
18+
# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser
19+
20+
blank_issues_enabled: false
21+
22+
contact_links:
23+
24+
- name: Project Mailing Lists
25+
url: https://maven.apache.org/mailing-lists.html
26+
about: Please ask a question or discuss here
27+
28+
- name: Old JIRA Issues
29+
url: https://issues.apache.org/jira/projects/MPIR
30+
about: Please search old JIRA issues

‎.github/pull_request_template.md

+13-19
Original file line numberDiff line numberDiff line change
@@ -1,29 +1,23 @@
1-
Following this checklist to help us incorporate your
1+
Following this checklist to help us incorporate your
22
contribution quickly and easily:
33

4-
- [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MPIR) filed
5-
for the change (usually before you start working on it). Trivial changes like typos do not
6-
require a JIRA issue. Your pull request should address just this issue, without
7-
pulling in other changes.
8-
- [ ] Each commit in the pull request should have a meaningful subject line and body.
9-
- [ ] Format the pull request title like `[MPIR-XXX] - Fixes bug in ApproximateQuantiles`,
10-
where you replace `MPIR-XXX` with the appropriate JIRA issue. Best practice
11-
is to use the JIRA issue title in the pull request title and in the first line of the
12-
commit message.
13-
- [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
14-
- [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will
15-
be performed on your pull request automatically.
16-
- [ ] You have run the integration tests successfully (`mvn -Prun-its clean verify`).
4+
- [ ] Your pull request should address just one issue, without pulling in other changes.
5+
- [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
6+
- [ ] Each commit in the pull request should have a meaningful subject line and body.
7+
Note that commits might be squashed by a maintainer on merge.
8+
- [ ] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
9+
This may not always be possible but is a best-practice.
10+
- [ ] Run `mvn verify` to make sure basic checks pass.
11+
A more thorough check will be performed on your pull request automatically.
12+
- [ ] You have run the integration tests successfully (`mvn -Prun-its verify`).
1713

1814
If your pull request is about ~20 lines of code you don't need to sign an
1915
[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
2016
please ask on the developers list.
2117

22-
To make clear that you license your contribution under
18+
To make clear that you license your contribution under
2319
the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
2420
you have to acknowledge this by using the following check-box.
2521

26-
- [ ] 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)
27-
28-
- [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
29-
22+
- [ ] 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)
23+
- [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).

‎README.md

-17
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,6 @@
1717
Contributing to [Apache Maven Project Info Reports Plugin](https://maven.apache.org/plugins/maven-project-info-reports-plugin/)
1818
======================
1919

20-
[![ASF Jira](https://img.shields.io/endpoint?url=https%3A%2F%2Fmaven.apache.org%2Fbadges%2Fasf_jira-MPIR.json)][jira]
2120
[![Apache License, Version 2.0, January 2004](https://img.shields.io/github/license/apache/maven.svg?label=License)][license]
2221
[![Maven Central](https://img.shields.io/maven-central/v/org.apache.maven.plugins/maven-project-info-reports-plugin.svg?label=Maven%20Central)](https://search.maven.org/artifact/org.apache.maven.plugins/maven-project-info-reports-plugin)
2322
[![Reproducible Builds](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/jvm-repo-rebuild/reproducible-central/master/content/org/apache/maven/plugins/maven-project-info-reports-plugin/badge.json)](https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/maven/plugins/maven-project-info-reports-plugin/README.md)
@@ -34,7 +33,6 @@ things.
3433
Getting Started
3534
---------------
3635

37-
+ Make sure you have a [JIRA account](https://issues.apache.org/jira/).
3836
+ Make sure you have a [GitHub account](https://github.com/signup/free).
3937
+ If you're planning to implement a new feature, it makes sense to discuss your changes
4038
on the [dev list][ml-list] first.
@@ -60,25 +58,12 @@ There are some guidelines which will make applying PRs easier for us:
6058
+ Create minimal diffs - disable on save actions like reformat source code or organize imports.
6159
If you feel the source code should be reformatted, create a separate PR for this change.
6260
+ Check for unnecessary whitespace with `git diff --check` before committing.
63-
+ Make sure your commit messages are in the proper format. Your commit message should contain the key of the JIRA issue.
64-
```
65-
[MPIR-XXX] - Subject of the JIRA Ticket
66-
Optional supplemental description.
67-
```
6861
+ Make sure you have added the necessary tests (JUnit/IT) for your changes.
6962
+ Run all the tests with `mvn -Prun-its verify` to assure nothing else was accidentally broken.
7063
+ Submit a pull request to the repository in the Apache organization.
71-
+ Update your JIRA ticket and include a link to the pull request in the ticket.
7264

7365
If you plan to contribute on a regular basis, please consider filing a [contributor license agreement][cla].
7466

75-
Making Trivial Changes
76-
----------------------
77-
78-
For changes of a trivial nature to comments and documentation, it is not always
79-
necessary to create a new ticket in JIRA. In this case, it is appropriate to
80-
start the first line of a commit with '(doc)' instead of a ticket number.
81-
8267
Additional Resources
8368
--------------------
8469

@@ -88,9 +73,7 @@ Additional Resources
8873
+ [General GitHub documentation](https://help.github.com/)
8974
+ [GitHub pull request documentation](https://help.github.com/send-pull-requests/)
9075
+ [Apache Maven Twitter Account](https://twitter.com/ASFMavenProject)
91-
+ #Maven IRC channel on freenode.org
9276

93-
[jira]: https://issues.apache.org/jira/projects/MPIR/
9477
[license]: https://www.apache.org/licenses/LICENSE-2.0
9578
[ml-list]: https://maven.apache.org/mailing-lists.html
9679
[code-style]: https://maven.apache.org/developers/conventions/code.html

‎pom.xml

+2-28
Original file line numberDiff line numberDiff line change
@@ -99,8 +99,8 @@ under the License.
9999
<url>https://github.com/apache/maven-project-info-reports-plugin/tree/${project.scm.tag}</url>
100100
</scm>
101101
<issueManagement>
102-
<system>JIRA</system>
103-
<url>https://issues.apache.org/jira/browse/MPIR</url>
102+
<system>GitHub</system>
103+
<url>https://github.com/apache/maven-project-info-reports-plugin/isuess</url>
104104
</issueManagement>
105105
<ciManagement>
106106
<system>Jenkins</system>
@@ -453,32 +453,6 @@ under the License.
453453
</reporting>
454454

455455
<profiles>
456-
<profile>
457-
<id>reporting</id>
458-
<reporting>
459-
<plugins>
460-
<plugin>
461-
<groupId>org.apache.maven.plugins</groupId>
462-
<artifactId>maven-changes-plugin</artifactId>
463-
<configuration>
464-
<!-- For JIRA report -->
465-
<columnNames>Type,Key,Summary,Assignee</columnNames>
466-
<maxEntries>200</maxEntries>
467-
<onlyCurrentVersion>true</onlyCurrentVersion>
468-
<resolutionIds>Fixed</resolutionIds>
469-
<sortColumnNames>Type,Key</sortColumnNames>
470-
</configuration>
471-
<reportSets>
472-
<reportSet>
473-
<reports>
474-
<report>jira-report</report>
475-
</reports>
476-
</reportSet>
477-
</reportSets>
478-
</plugin>
479-
</plugins>
480-
</reporting>
481-
</profile>
482456
<profile>
483457
<id>run-its</id>
484458
<properties>

0 commit comments

Comments
 (0)