|
| 1 | +# Description of changes <!-- to be filled in --> |
| 2 | + |
| 3 | +<!-- Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change. --> |
| 4 | + |
| 5 | +## Type of change <!-- to be filled in --> |
| 6 | + |
| 7 | +Please delete options that are not relevant. |
| 8 | + |
| 9 | +- [ ] Bug fix (non-breaking change which fixes an issue) |
| 10 | +- [ ] New feature (non-breaking change which adds functionality) |
| 11 | +- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) |
| 12 | +- [ ] This change requires a documentation update |
| 13 | + |
| 14 | +## All Submissions <!-- to be checked --> |
| 15 | + |
| 16 | +- [ ] Have you checked to ensure there aren't other open [Pull Requests](../../../pulls) for the same update/change? |
| 17 | +- [ ] Have you made a descriptive commit message with a short title (first line). |
| 18 | +- [ ] Have you performed a self-review of your code |
| 19 | +- [ ] Have you commented your code, particularly in hard-to-understand areas |
| 20 | +- [ ] Have you made corresponding changes to the documentation |
| 21 | +- [ ] Have you added tests that prove your fix is effective or that your feature works |
| 22 | +- [ ] My changes generate no new warnings or errors of any kind |
| 23 | +- [ ] You have done your changes in a separate branch. |
| 24 | +- [ ] Branch has descriptive name that start with either the `bug/` or `feature/` prefixes. <!-- Good examples are: 'bug/signin-issue' or 'feature/issue-templates'. --> |
| 25 | + |
| 26 | +**After** these steps, you're ready to open a pull request. |
| 27 | + |
| 28 | +- [ ] Give a descriptive title to your PR. |
| 29 | +- [ ] Describe your changes. |
| 30 | +- [ ] Put `closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such). |
| 31 | + |
| 32 | +### New Feature Submissions <!-- to be filled in if relevant or remove --> |
| 33 | + |
| 34 | +1. [ ] Does your submission pass tests? |
| 35 | +2. [ ] Have you lint your code locally before submission? |
| 36 | + |
| 37 | +# How Has This Been Tested? <!-- to be filled in --> |
| 38 | + |
| 39 | +1. Please describe the tests that you ran to verify your changes. |
| 40 | +2. Provide instructions so we can reproduce. |
| 41 | +3. Please list any relevant details for your test configuration |
| 42 | + |
| 43 | +- [ ] Test A |
| 44 | +- [ ] Test B |
| 45 | + |
| 46 | +**Test Configuration**: |
| 47 | +- mLauncher version: |
| 48 | +- Device name: |
| 49 | +- Android version: |
| 50 | +- Other information: |
| 51 | + |
0 commit comments