-
Notifications
You must be signed in to change notification settings - Fork 190
Align PR template (3.x) #1103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Align PR template (3.x) #1103
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,29 +1,23 @@ | ||
| Following this checklist to help us incorporate your | ||
| 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/MCOMPILER) 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 `[MCOMPILER-XXX] - Fixes bug in ApproximateQuantiles`, | ||
| where you replace `MCOMPILER-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 verify` to make sure basic checks pass. A more thorough check will | ||
| be performed on your pull request automatically. | ||
| - [ ] You have run the integration tests successfully (`mvn -Prun-its clean verify`). | ||
| - [ ] 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. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not helpful. We don't bother paying attention to individual commit messages. Just keep the PR description reasonable (and with LLMs they're getting better lately) |
||
| 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. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. unit or integration |
||
| 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 integration tests successfully (`mvn -Prun-its verify`). | ||
|
|
||
| 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 | ||
| please ask on the developers list. | ||
|
|
||
| To make clear that you license your contribution under | ||
| To make clear that you license your contribution under | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Acknowledge that you license this 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) | ||
|
|
||
| - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). | ||
|
|
||
| - [ ] 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). | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I have filed an Apache Individual Contributor License Agreement. |
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Following --> Follow