|
| 1 | +# Contributing to WooCommerce Custom Order Tables |
| 2 | + |
| 3 | +Thank you for your interest in WooCommerce Custom Order Tables! |
| 4 | + |
| 5 | + |
| 6 | +## Reporting bugs and/or suggesting new features |
| 7 | + |
| 8 | +We welcome input from the community on new features for the plugin, as well as reports of anything that doesn't seem to be working properly. |
| 9 | + |
| 10 | +To make a suggestion or report a bug, please [create a new issue within the GitHub repository](https://github.com/liquidweb/woocommerce-order-tables/issues/new) with a descriptive title and as much pertinent information as possible. |
| 11 | + |
| 12 | +When reporting a bug, please include the following information: |
| 13 | + |
| 14 | +* Steps to reproduce (what steps would someone need to take to see the bug in action?) |
| 15 | +* The expected behavior (what _should_ happen?) |
| 16 | +* The observed behavior (what _is_ happening?) |
| 17 | +* Information about your WooCommerce instance — this can easily be obtained via the WooCommerce › Status screen, via the "Get system report" button at the top of that page. |
| 18 | + |
| 19 | + |
| 20 | +## Contributing code |
| 21 | + |
| 22 | +If you're interested in contributing to the plugin by way of code and/or documentation, please read the following details about the structure of the project: |
| 23 | + |
| 24 | + |
| 25 | +### Coding conventions |
| 26 | + |
| 27 | +This project adheres to the [WordPress coding standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/), and [an `.editorconfig` file](http://editorconfig.org/) is included in the repository to help most <abbr title="Integrated Development Environment">IDE</abbr>s adjust accordingly. |
| 28 | + |
| 29 | + |
| 30 | +### Branching strategy |
| 31 | + |
| 32 | +This project uses [Gitflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) as a branching strategy: |
| 33 | + |
| 34 | +* `develop` represents the current development version, whereas `master` represents the latest stable release. |
| 35 | +* All work should be done in separate feature branches, which should be branched from `develop`. |
| 36 | + |
| 37 | + |
| 38 | +#### Tagging a new release |
| 39 | + |
| 40 | +When a new release is being prepared, a new `release/vX.X.X` branch will be created from `develop`, version numbers bumped and any last-minute release adjustments made, then the release branch will be merged (via non-fast-forward merge) into `master`. |
| 41 | + |
| 42 | +Once master has been updated, the release should be tagged, then `master` should be merged into `develop`. |
| 43 | + |
| 44 | + |
| 45 | +### Unit testing |
| 46 | + |
| 47 | +WooCommerce Custom Order Tables uses [the WordPress core testing suite](https://make.wordpress.org/core/handbook/testing/automated-testing/writing-phpunit-tests/) to provide automated tests for its functionality. |
| 48 | + |
| 49 | +When submitting pull requests, please include relevant tests for your new features and bugfixes. This helps prevent regressions in future iterations of the plugin, and helps instill confidence in store owners using this to enhance their WooCommerce stores. |
0 commit comments