PluginProbe ʕ •ᴥ•ʔ
Kubio AI Page Builder / trunk
Kubio AI Page Builder vtrunk
2.9.0 2.8.6 2.8.5 2.8.4 2.8.3 2.8.2 2.8.1 trunk 1.0.0 1.0.1 1.1.0 1.2.0 1.2.1 1.2.2 1.2.3 1.3.0 1.3.1 1.3.2 1.4.0 1.4.1 1.4.2 1.4.3 1.5.0 1.6.0 1.6.1 1.6.2 1.6.3 1.6.4 1.7.0 1.7.1 1.7.2 1.7.3 1.8.0 1.8.1 1.8.2 1.9.0 2.0.0 2.1.1 2.1.2 2.1.3 2.2.0 2.2.3 2.2.4 2.2.5 2.3.0 2.3.1 2.3.3 2.3.4 2.4.0 2.4.1 2.4.2 2.4.3 2.4.5 2.5.0 2.5.1 2.5.2 2.5.3 2.6.0 2.6.1 2.6.2 2.6.3 2.6.5 2.6.6 2.6.7 2.7.0 2.7.1 2.7.2 2.7.3 2.8.0
kubio / vendor / pragmarx / ia-str / PULL_REQUEST_TEMPLATE.md
kubio / vendor / pragmarx / ia-str Last commit date
src 1 year ago stubs 4 years ago .styleci.yml 4 years ago CHANGELOG.md 4 years ago CODE_OF_CONDUCT.md 4 years ago CONTRIBUTING.md 4 years ago ISSUE_TEMPLATE.md 4 years ago LICENSE.md 4 years ago PULL_REQUEST_TEMPLATE.md 4 years ago README.md 4 years ago composer.json 1 year ago phpunit.xml 4 years ago upgrade.sh 4 years ago
PULL_REQUEST_TEMPLATE.md
44 lines
1 <!--- Provide a general summary of your changes in the Title above -->
2
3 ## Description
4
5 Describe your changes in detail.
6
7 ## Motivation and context
8
9 Why is this change required? What problem does it solve?
10
11 If it fixes an open issue, please link to the issue here (if you write `fixes #num`
12 or `closes #num`, the issue will be automatically closed when the pull is accepted.)
13
14 ## How has this been tested?
15
16 Please describe in detail how you tested your changes.
17
18 Include details of your testing environment, and the tests you ran to
19 see how your change affects other areas of the code, etc.
20
21 ## Screenshots (if appropriate)
22
23 ## Types of changes
24
25 What types of changes does your code introduce? Put an `x` in all the boxes that apply:
26 - [ ] Bug fix (non-breaking change which fixes an issue)
27 - [ ] New feature (non-breaking change which adds functionality)
28 - [ ] Breaking change (fix or feature that would cause existing functionality to change)
29
30 ## Checklist:
31
32 Go over all the following points, and put an `x` in all the boxes that apply.
33
34 Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our [](http://www.phptherightway.com/#continuous-integrationcontinuous integration](http://www.phptherightway.com/#continuous-integration](http://www.phptherightway.com/#continuous-integration) server to make sure your [](https://help.github.com/articles/about-required-status-checks/tests and code style pass](https://help.github.com/articles/about-required-status-checks/](https://help.github.com/articles/about-required-status-checks/).
35
36 - [ ] I have read the **[](CONTRIBUTING.mdCONTRIBUTING](CONTRIBUTING.md](CONTRIBUTING.md)** document.
37 - [ ] My pull request addresses exactly one patch/feature.
38 - [ ] I have created a branch for this patch/feature.
39 - [ ] Each individual commit in the pull request is meaningful.
40 - [ ] I have added tests to cover my changes.
41 - [ ] If my change requires a change to the documentation, I have updated it accordingly.
42
43 If you're unsure about any of these, don't hesitate to ask. We're here to help!
44