PHP JavaScript CSS Other
Permalink
Failed to load latest commit information.
.github Update CONTRIBUTING.md Feb 21, 2017
apigen Adjusts all references of 'woothemes' to 'woocommerce' in relevant UR… Sep 28, 2016
assets Merge pull request #13306 from woocommerce/fix-13303 Feb 23, 2017
dummy-data colour -> color Dec 19, 2016
i18n Fixed coding standards Feb 24, 2017
includes Fixed coding standards Feb 24, 2017
templates Move account wrapper to prevent field reordering Feb 23, 2017
tests Fixed coding standards Feb 24, 2017
.codeclimate.yml Ratings for codeclimate Nov 23, 2016
.coveralls.yml Add coveralls.io for tracking test coverage Sep 7, 2014
.editorconfig HTTPS for everybody May 27, 2016
.gitignore Add CLI tests Dec 8, 2016
.jshintrc Tweaks JSHint for cart and cart fragments Jun 10, 2015
.scrutinizer.yml Exclude legacy from quality check Feb 17, 2017
.stylelintrc Cleaned up SCSS files so they lint and made some rules warnings Aug 10, 2016
.travis.yml Unquote 7.1 in .travis.yml Jan 17, 2017
CHANGELOG.txt Updated changelog Feb 24, 2017
Gruntfile.js Minify Feb 16, 2017
README.md Update README.md Dec 7, 2016
apigen.neon WIP - Product CRUD (#12065) Nov 16, 2016
composer.json Merge branch 'fix-12922' Jan 26, 2017
composer.lock Update composer dependencies using --prefer-stable #11980 Sep 28, 2016
license.txt upstream Feb 19, 2015
package.json Move admin.css select2 dependency to gruntfile Feb 10, 2017
phpcs.ruleset.xml Allow CodeSniffer throw alerts about wp_get_post_terms functions Nov 17, 2016
phpunit.xml Add PHPUnit coverage `addUncoveredFilesFromWhitelist="true"` Jan 17, 2017
phpunit.xml.dist Add PHPUnit coverage `addUncoveredFilesFromWhitelist="true"` Jan 17, 2017
readme.txt Updated changelog Feb 24, 2017
uninstall.php PEAR.Functions.FunctionCallSignature.SpaceAfterOpenBracket Sep 2, 2016
woocommerce.php 2.7 beta 4 Feb 24, 2017

README.md

WooCommerce Built with Grunt Build Status Code Coverage Scrutinizer Code Quality Code Climate

Welcome to the WooCommerce repository on GitHub. Here you can browse the source, look at open issues and keep track of development. We recommend all developers to follow the WooCommerce development blog to stay up to date about everything happening in the project. You can also follow @DevelopWC on Twitter for the latest development updates.

If you are not a developer, please use the WooCommerce plugin page on WordPress.org.

Documentation

Reporting Security issues

To disclose a security issue to our team, please submit a report via HackerOne here.

Support

This repository is not suitable for support. Please don't use our issue tracker for support requests, but for core WooCommerce issues only. Support can take place in the appropriate channels:

Support requests in issues on this repository will be closed on sight.

Contributing to WooCommerce

If you have a patch, or stumbled upon an issue with WooCommerce core, you can contribute this back to the code. Please read our contributor guidelines for more information how you can do this.