Skip to content

Latest commit

 

History

History
43 lines (30 loc) · 1.78 KB

CONTRIBUTING.md

File metadata and controls

43 lines (30 loc) · 1.78 KB

Thanks for reading our contribution guidelines! What do you want to do:

How to write a useful bug report

If you think you have found a bug, please make sure you're using the latest version of the plugin. If possible check out the latest version from GitHub and see if the bug still exists there.

A useful bug report explains:

  1. What you were trying to achieve.
  2. What you were expecting to happen.
  3. What actually happened, illustrated with screenshots if possible.

Your bug report should also contain your WordPress version and if there are any errors, the exact error text, including line numbers.

#Security issues If you find a security issue please do not report security issues here, but email them to aron at atomace dot com so it can be dealt with securely and quickly.

#Contribute to Drafty In Here

When contributing please ensure you follow the guidelines below.

Making Changes

  • Fork the repository on GitHub (make sure to use the development branch, not master).
  • Make the changes to your forked repository.
  • Where possible follow the WordPress Coding Standards.
  • When committing, your commit message should start with [fix], [update], or [add] depending on the type of change.
  • Push the changes to your fork and submit a pull request to the 'development' branch of the Drafty In Here repository.

All pull requests will be review and if necessary changes will be made.

Additional Resources