File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed
Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change 11Following this checklist to help us incorporate your
22contribution quickly and easily:
33
4- - [ ] Make sure there is a [ JIRA issue] ( https://issues.apache.org/jira/browse/MPH ) filed
4+ - [ ] Make sure there is a [ JIRA issue] ( https://issues.apache.org/jira/browse/MDEPLOY ) filed
55 for the change (usually before you start working on it). Trivial changes like typos do not
66 require a JIRA issue. Your pull request should address just this issue, without
77 pulling in other changes.
88 - [ ] Each commit in the pull request should have a meaningful subject line and body.
9- - [ ] Format the pull request title like ` [MPH -XXX] - Fixes bug in ApproximateQuantiles ` ,
10- where you replace ` MPH -XXX` with the appropriate JIRA issue. Best practice
9+ - [ ] Format the pull request title like ` [MDEPLOY -XXX] - Fixes bug in ApproximateQuantiles ` ,
10+ where you replace ` MDEPLOY -XXX` with the appropriate JIRA issue. Best practice
1111 is to use the JIRA issue title in the pull request title and in the first line of the
1212 commit message.
1313 - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
You can’t perform that action at this time.
0 commit comments