PluginProbe ʕ •ᴥ•ʔ
Kubio AI Page Builder / 2.8.6
Kubio AI Page Builder v2.8.6
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 / CONTRIBUTING.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
CONTRIBUTING.md
33 lines
1 # Contributing
2
3 Contributions are **welcome** and will be fully **credited**.
4
5 We accept contributions via Pull Requests on [](https://github.com/pragmarx/coollectionGithub](https://github.com/pragmarx/coollection](https://github.com/pragmarx/coollection).
6
7
8 ## Pull Requests
9
10 - **[](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.mdPSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md)** - Check the code style with ``$ composer check-style`` and fix it with ``$ composer fix-style``.
11
12 - **Add tests!** - Your patch won't be accepted if it doesn't have tests.
13
14 - **Document any change in behaviour** - Make sure the `README.md` and any other relevant documentation are kept up-to-date.
15
16 - **Consider our release cycle** - We try to follow [](http://semver.org/SemVer v2.0.0](http://semver.org/](http://semver.org/). Randomly breaking public APIs is not an option.
17
18 - **Create feature branches** - Don't ask us to pull from your master branch.
19
20 - **One pull request per feature** - If you want to do more than one thing, send multiple pull requests.
21
22 - **Send coherent history** - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please [](http://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messagessquash them](http://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages](http://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting.
23
24
25 ## Running Tests
26
27 ``` bash
28 $ composer test
29 ```
30
31
32 **Happy coding**!
33