Steve-Dee-Designs
/
woocommerce
mirror of https://github.com/woocommerce/woocommerce.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
woocommerce/tools/code-analyzer
History
Sam Seay 41a276c49b
Pass the version argument explicitly to code-analyzer, introduce a new command that determines latest major/minor (#34404) 
This also adds a new command `major_minor` that contains some of the old logic of `getPluginData` to determine the latest major/minor version of WooCommerce
 		2022-08-22 16:29:59 +12:00
..
bin CLI tool and GH workflow to highlight PR changes (#32063) 2022-05-17 13:47:17 +12:00
src Pass the version argument explicitly to code-analyzer, introduce a new command that determines latest major/minor (#34404) 2022-08-22 16:29:59 +12:00
.eslintignore CLI tool and GH workflow to highlight PR changes (#32063) 2022-05-17 13:47:17 +12:00
.eslintrc CLI tool and GH workflow to highlight PR changes (#32063) 2022-05-17 13:47:17 +12:00
.gitignore CLI tool and GH workflow to highlight PR changes (#32063) 2022-05-17 13:47:17 +12:00
README.md Pass the version argument explicitly to code-analyzer, introduce a new command that determines latest major/minor (#34404) 2022-08-22 16:29:59 +12:00
package.json Simplify turbo commands (#34055) 2022-08-05 12:03:17 +12:00
tsconfig.json Migrate From Nx to Turborepo (#33079) 2022-06-09 14:40:07 -07:00

README.md

Code Analyzer

Description

code-analyzer is a CLI tool designed to analyze change information about plugins in the WooCommerce monorepo.

Commands

Currently there are just 2 commands:

  1. analyzer. Analyzer serves 2 roles currently, as a linter for PRs to check if introduced hook/template/db changes have associated changelog entries and also to provide file output of changes between WooCommerce versions for the purpose of automating release processes (such as generating release posts.)

Here is an example analyzer command:

./bin/dev analyzer release/6.8 "6.8.0" -b=release/6.7

In this command we compare the release/6.7 and release/6.8 branches to find differences, and we're looking for changes introduced since 6.8.0 (using the @since tag).

To find out more about the other arguments to the command you can run ./bin/dev analyzer --help

  1. major_minor. This simple CLI tool gives you the latest .0 major/minor released version of a plugin's mainfile based on Woo release conventions.

Here is an example major_minor command:

./bin/dev major_minor release/6.8 "plugins/woocommerce/woocommerce.php"

In this command we checkout the branch release/6.8 and check the version of the woocommerce.php mainfile located at the path passed. Note that at the time of writing the main file in this particular branch reports 6.8.1 so the output of this command is 6.8.0.

This command is particularly useful combined with the analyzer, allowing you to determine the last major/minor.0 version of a branch or ref before passing that as the version argument to analyzer.