Skip to content

Latest commit

 

History

History
135 lines (82 loc) · 5.97 KB

CONTRIBUTING.md

File metadata and controls

135 lines (82 loc) · 5.97 KB

Contributing to WP Crontrol

Bug reports, code contributions, and general feedback are very welcome. These should be submitted through the GitHub repository. Development happens in the develop branch, and any pull requests should be made against that branch please.

Reviews on WordPress.org

If you enjoy using WP Crontrol I would greatly appreciate it if you left a positive review on the WordPress.org Plugin Directory. This is the fastest and easiest way to contribute to WP Crontrol 😄.

Reporting Security Issues

If you discover a security issue in WP Crontrol, please report it to the security program on HackerOne. Do not report security issues on GitHub or the WordPress.org support forums. Thank you.

Inclusivity and Code of Conduct

Contributions to WP Crontrol are welcome from anyone. Whether you are new to Open Source or a seasoned veteran, all constructive contribution is welcome and I'll endeavour to support you when I can.

This project is released with a contributor code of conduct and by participating in this project you agree to abide by its terms. The code of conduct is nothing to worry about, if you are a respectful human being then all will be good.

Setting up Locally

You can clone this repo into your wp-content/plugins directory but you'll need to install the development dependencies before activating the plugin.

Prerequisites

Setup

Install the PHP dependencies:

composer install

Running the Tests

The test suite includes acceptance tests which run in a Docker container. Ensure Docker Desktop is running before running the tests.

To run the whole test suite which includes PHPCS code sniffs, PHPStan static analysis, and WPBrowser acceptance tests:

composer test

To run just the code sniffs:

composer test:cs

To run just the static analysis:

composer test:phpstan

To run just the acceptance tests:

composer test:acceptance

If you're repeatedly running the tests during development, to speed things up you can start and stop the containers manually and then they won't be started and stopped each time you run the tests:

composer test:start
composer test
composer test
composer test
composer test:stop

Releasing a New Version

These are the steps to take to release a new version of WP Crontrol (for contributors who have push access to the GitHub repo).

Prior to Release

  1. Check the milestone on GitHub for open issues or PRs. Fix or reassign as necessary.

  2. If this is a non-patch release, check issues and PRs assigned to the patch or minor milestones that will get skipped. Reassign as necessary.

  3. Ensure you're on the develop branch and all the changes for this release have been merged in.

  4. Ensure readme.md contains up to date descriptions, "Tested up to" versions, FAQs, screenshots, etc.

  5. Ensure .gitattributes is up to date with all files that shouldn't be part of the build.

    • To do this, export the archive then check the contents for files that shouldn't be part of the package:

      git archive --output=wp-crontrol.zip HEAD

  6. Run the tests and ensure everything passes:

    composer test

  7. Prepare a changelog for the Releases page on GitHub.

For Release

  1. Install the Node dependencies:

    npm install

  2. Bump the plugin version number:

    • For a patch release (1.2.3 => 1.2.4):

      npm run bump:patch

    • For a minor release (1.2.3 => 1.3.0):

      npm run bump:minor

    • For a major release (1.2.3 => 2.0.0):

      npm run bump:major

  3. git push origin develop

  4. Wait until (and ensure that) the build passes

  5. git checkout master

  6. git merge develop

  7. git push origin master

  8. git push origin master:release

  9. Wait for the Build Release action to complete

  10. Enter the changelog into the release on GitHub and publish it.

Post Release

Publishing a release on GitHub triggers an action which deploys the release to the WordPress.org Plugin Directory. No need to touch Subversion.

New milestones are automatically created for the next major, minor, and patch releases where appropriate.

  1. Close the milestone.
  2. If this is a non-patch release, manually delete any unused patch and minor milestones on GitHub.
  3. Check the new version has appeared on the WordPress.org plugin page (it'll take a few minutes).
  4. Resolve relevant threads on the plugin's support forums.
  5. Consume tea and cake as necessary.

Asset Updates

Assets such as screenshots and banners are stored in the .wordpress-org directory. These get deployed as part of the automated release process too.

In order to deploy only changes to assets, push the change to the deploy branch and they will be deployed if they're the only changes in the branch since the last release. This allows for the "Tested up to" value to be bumped as well as assets to be updated in between releases.