Skip to content

Commit

Permalink
final beta of 2.8.2?
Browse files Browse the repository at this point in the history
  • Loading branch information
futtta committed Mar 13, 2021
1 parent e3099e0 commit 2bb3749
Show file tree
Hide file tree
Showing 2 changed files with 22 additions and 2 deletions.
4 changes: 2 additions & 2 deletions autoptimize.php
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
* Plugin Name: Autoptimize
* Plugin URI: https://autoptimize.com/
* Description: Makes your site faster by optimizing CSS, JS, Images, Google fonts and more.
* Version: 2.8.2-beta-3
* Version: 2.8.2-beta-4
* Author: Frank Goossens (futtta)
* Author URI: https://autoptimize.com/
* Text Domain: autoptimize
Expand All @@ -21,7 +21,7 @@
exit;
}

define( 'AUTOPTIMIZE_PLUGIN_VERSION', '2.8.2-beta-3' );
define( 'AUTOPTIMIZE_PLUGIN_VERSION', '2.8.2-beta-4' );

// plugin_dir_path() returns the trailing slash!
define( 'AUTOPTIMIZE_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
Expand Down
20 changes: 20 additions & 0 deletions contributing.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
Issues
==
If you are a plugin user who has problems configuring Autoptimize (your site breaking in some way when activating AO) **the place to get help is [the Autoptimize support forum at wordpress.org](https://wordpress.org/support/plugin/autoptimize/)**.

If you are a developer and you think you discovered a bug in the code or if you have ideas for improvements, create an issue here on Github with a clear technical description.

If you are both developer & plugin user the choice is yours (it really depends on what type of support you need) ;-)

Pull requests
==
PR's are enthousiastically welcomed!

For optimal efficiency please take the following things into account:
1. use the **beta** branch as master is frozen to be at the same level as the current version on wordpress.org.
2. test your changes not only functionally, but also using the **unit tests** available (running `composer test` after having done `composer install` and running `bin/install-wp-tests.sh`)
3. (new) code is supposed to follow the WordPress code guidelines, test using **phpcs** (install with `composer install` and then run `vendor/squizlabs/bin/phpcs` against your changed/ added file

When in doubt or in need of guidance/ help create an issue describing what you would like to change and we'll figure it out! :-)

Frank

0 comments on commit 2bb3749

Please sign in to comment.