Did you know that you could be instrumental in making Jetpack more robust and secure? If you use and love Jetpack, why not contribute to the project?
Whether you can barely recognize a filter (or don’t know what that means) or you’ve already authored your own plugins, there are ways for you to pitch in.
Beta testers give updates, fixes, and new modules a test run before they’re publicly released, so they’re an important part of the development process. If you'd like to join our Beta group, sign up to be a Beta tester here.
If you find a bug, let us know by creating a new issue here. You can check our recommendations to create great bug reports here.
If you'd like to fix a bug, you can submit a Pull Request. Follow these detailed steps to find out how.
When creating Pull Requests, remember:
- Check In Early, Check In Often.
- Write good commit messages.
- Respect the Best practices for WordPress development.
There are a few bonuses that can increase the chances that your Pull Request is accepted:
- If you've created a new action or filter, add inline documentation to help others understand how to use the action or the filter.
- Create unit tests if you can. If you're not familiar with Unit Testing, you can check this tutorial.
- If Grunt is installed on your testing environmenent, run it after committing your changes. It will allow you to detect errors in Javascript files, compile Sass to CSS, and a few other things.
If you'd like to contribute but don't know where to get started, you can take a look at existing issues:
- "Good First Bug" issues are a good entry point to get familiar with Jetpack's codebase.
- All issues labeled with the "Community" milestone are fair game. That's a great way to contribute new features and fix small issues within Jetpack.
- "Whisky" issues are important bugs or enhancements. Take a crack at it if you feel adventurous! :)