wp-staging
Last commit date
Backend
1 year ago
Backup
1 year ago
Basic
2 years ago
Core
2 years ago
Duplicator
2 years ago
Framework
1 year ago
Frontend
2 years ago
Notifications
2 years ago
assets
1 year ago
languages
3 years ago
vendor_wpstg
1 year ago
CONTRIBUTING.md
2 years ago
Deactivate.php
2 years ago
README.md
2 years ago
SECURITY.md
2 years ago
autoloader.php
3 years ago
bootstrap.php
2 years ago
constantsFree.php
1 year ago
freeBootstrap.php
2 years ago
install.php
2 years ago
opcacheBootstrap.php
1 year ago
readme.txt
1 year ago
runtimeRequirements.php
2 years ago
uninstall.php
2 years ago
wp-staging-error-handler.php
2 years ago
wp-staging.php
1 year ago
CONTRIBUTING.md
39 lines
| 1 | #Contribute To WP Staging |
| 2 | |
| 3 | Community made patches, localisations, bug reports and contributions are always welcome. |
| 4 | |
| 5 | When contributing please ensure you follow the guidelines below so that we can keep on top of things. |
| 6 | |
| 7 | __Please Note:__ GitHub is for bug reports and contributions only. |
| 8 | |
| 9 | ## Getting Started |
| 10 | |
| 11 | * Submit a ticket for your issue, assuming one does not already exist. |
| 12 | * Raise it on our [](https://github.com/WP-Staging/wp-staging/issuesIssue Tracker](https://github.com/WP-Staging/wp-staging/issues](https://github.com/WP-Staging/wp-staging/issues) |
| 13 | * Clearly describe the issue including steps to reproduce the bug. |
| 14 | * Make sure you fill in the earliest version that you know has the issue as well as the version of WordPress you're using. |
| 15 | |
| 16 | ## Making Changes |
| 17 | |
| 18 | * Fork the repository on GitHub |
| 19 | * Make the changes to your forked repository |
| 20 | * Ensure you stick to the PSR standard |
| 21 | * When committing, reference your issue (if present) and include a note about the fix |
| 22 | * (coming soon) If possible, and if applicable, please also add/update unit tests for your changes |
| 23 | * Push the changes to your fork and submit a pull request to the 'master' branch of the WP Staging repository |
| 24 | |
| 25 | ## Code Documentation |
| 26 | |
| 27 | * We ensure that every WP Staging function is documented well and follows the standards set by phpDoc |
| 28 | * An example function can be found [](https://gist.github.com/rene-hermenau/8d3d7ee0633ee2f64b4bhere](https://gist.github.com/rene-hermenau/8d3d7ee0633ee2f64b4b](https://gist.github.com/rene-hermenau/8d3d7ee0633ee2f64b4b) |
| 29 | * Please make sure that every function is documented so that when we update our API Documentation it will complete |
| 30 | * If you're adding/editing a function in a class, make sure to add `@access {private|public|protected}` |
| 31 | * Finally, please use tabs and not spaces. The tab indent size should be 4 for all WP Staging code. |
| 32 | |
| 33 | At this point you're waiting on us to merge your pull request. We'll review all pull requests, and make suggestions and changes if necessary. |
| 34 | |
| 35 | # Additional Resources |
| 36 | * [](http://help.github.com/General GitHub Documentation](http://help.github.com/](http://help.github.com/) |
| 37 | * [](http://help.github.com/send-pull-requests/GitHub Pull Request documentation](http://help.github.com/send-pull-requests/](http://help.github.com/send-pull-requests/) |
| 38 | * [](http://phpunit.de/manual/current/en/writing-tests-for-phpunit.htmlPHPUnit Tests Guide](http://phpunit.de/manual/current/en/writing-tests-for-phpunit.html](http://phpunit.de/manual/current/en/writing-tests-for-phpunit.html) |
| 39 |