Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
36 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,36 @@ | ||
| **Thank you for wanting to contribute to WP Rocket! Before submitting a pull request, please check that you’ve completed the following steps:** | ||
| - Please make sure that there aren’t existing pull requests attempting to address the issue mentioned. | ||
| - Check for related issues on the issue tracker. | ||
| - Non-trivial changes should be discussed on an issue first. | ||
| - Let us know you’re working on the issue. | ||
| - Develop in a topic branch, not master. | ||
|
|
||
| **Things to add in the pull request to help us:** | ||
| - Provide useful pull request description. | ||
| - Follow project commit guidelines. | ||
| - Write a good description of your PR. | ||
| - Link to the Github issue in the description. | ||
| ## Description | ||
|
|
||
| Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. | ||
|
|
||
| Fixes # (issue) | ||
|
|
||
| ## Type of change | ||
|
|
||
| Please delete options that are not relevant. | ||
|
|
||
| - [ ] Bug fix (non-breaking change which fixes an issue) | ||
| - [ ] New feature (non-breaking change which adds functionality) | ||
| - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) | ||
| - [ ] This change requires a documentation update | ||
|
|
||
| ## Is the solution different from the one proposed during the grooming? | ||
|
|
||
| Please describe in this section any change to the solution, and why. | ||
|
|
||
| ## How Has This Been Tested? | ||
|
|
||
| Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration | ||
|
|
||
| - [ ] Test A | ||
| - [ ] Test B | ||
|
|
||
| # Checklist: | ||
|
|
||
| - [ ] My code follows the style guidelines of this project | ||
| - [ ] I have performed a self-review of my own code | ||
| - [ ] I have commented my code, particularly in hard-to-understand areas | ||
| - [ ] I have made corresponding changes to the documentation | ||
| - [ ] My changes generate no new warnings | ||
| - [ ] I have added tests that prove my fix is effective or that my feature works | ||
| - [ ] New and existing unit tests pass locally with my changes | ||
| - [ ] Any dependent changes have been merged and published in downstream modules |