From 0264dcdc8aad61c123c4c214fc4e39069eee2ce4 Mon Sep 17 00:00:00 2001 From: Evan Mullins Date: Mon, 8 Jan 2024 11:30:06 -0500 Subject: [PATCH] add note about adding secondary module inputs --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 24102eb..02d079c 100644 --- a/README.md +++ b/README.md @@ -109,6 +109,7 @@ Refer to the [ecommerce module workflow PR](https://github.com/newfold-labs/wp-m ### Ideas for Improvement: +- Add an input to specify a secondary module repo and branch name to pull those changes in as well for integrated testing when corresponding changes are required in another module. (It should be enough to allow for one extra module change for now, if more are needed we can think through a json object or something.) - Add a flag to signify tests should run in Cypress cloud for easier debugging (devise a way to pass the plugin level key). - Add a flag to run for the full matrix of WP versions. - Add a flag to run for the full matrix of PHP versions. @@ -117,4 +118,4 @@ Refer to the [ecommerce module workflow PR](https://github.com/newfold-labs/wp-m - Update with wp-cli command(s) to update site state before running tests. Useful for running tests in another language or region, such as a hostgator-latam environment. ## Other Workflows -While this repository is still relatively new, we plan to add additional reusable workflows for managing plugins/modules in one central location. \ No newline at end of file +While this repository is still relatively new, we plan to add additional reusable workflows for managing plugins/modules in one central location.