What?
Mentioned in https://github.com/IDEMSInternational/parenting-app-ui/pull/2235#issuecomment-2020821493, we have a set of reusable workflows designed to be used from a content repo, however changes to these can only be tested post merge. Ideally we want to enable a better way to test a given branch action against a testing deployment repo branch.
Why?
Particularly for action updates that will impose breaking changes, good to clarify in advance that proposed changes work as intended instead of potentially requiring further iteration
How?
Likely some soft of reusable_workflow_test action that can be triggered from a branch using a workflow_dispatch, with inputs for the name of the workflow (possibly a dropdown list of reusable workflows), name of core branch (e.g. feat/workflow_updates), name and branchof target content repo (default to the debug_app/main repo) and possibly an input to override env variables for the run (e.g. json string that can be parsed and set to env as part of workflow).
This workflow should then trigger the related reusable workflow, passing parameters execute against the target deployment and source code.
NOTE - Should also confirm it is possible to use actions from a given target branch first
Other details
The reusable workflows might need minor modification if not already setup to allow core/content repo checkout at specific branches or tags
What? Mentioned in https://github.com/IDEMSInternational/parenting-app-ui/pull/2235#issuecomment-2020821493, we have a set of reusable workflows designed to be used from a content repo, however changes to these can only be tested post merge. Ideally we want to enable a better way to test a given branch action against a testing deployment repo branch.
Why? Particularly for action updates that will impose breaking changes, good to clarify in advance that proposed changes work as intended instead of potentially requiring further iteration
How? Likely some soft of
reusable_workflow_testaction that can be triggered from a branch using aworkflow_dispatch, with inputs for the name of the workflow (possibly a dropdown list of reusable workflows), name of core branch (e.g.feat/workflow_updates), name and branchof target content repo (default to the debug_app/main repo) and possibly an input to override env variables for the run (e.g. json string that can be parsed and set to env as part of workflow).This workflow should then trigger the related reusable workflow, passing parameters execute against the target deployment and source code.
NOTE - Should also confirm it is possible to use actions from a given target branch first
Other details The reusable workflows might need minor modification if not already setup to allow core/content repo checkout at specific branches or tags