Nov_Story F: As an operations user, I need a convenient way to create a test branch in lzim/mtl

[jamesmrollins]

User Story

The user currently must find and replace each link for the links below, throughout all lzim/mtl documentation:

• mtl.how/data -> mtl.how/data_test
• mtl.how/menu -> mtl.how/menu_test
• mtl.how/sim -> mtl.how/sim_test
• mtl.how -> mtl.how/test

This requires 4 separate runs of the find and replace action ( 8 runs, if one includes returning branch to Master), plus quality checks. The user would appreciate a standard action that would create a test branch and automatically change the links to Test. Therefore, any changes to the sim, documentation or related repository information can be achieved in the test branch, and then promoted to Master when ready.

Definition of Done

• [x] A completed GitHub action the user can call to create a test branch.
• [x] The GitHub action has been quality tested to ensure a stable action process.

[jamesmrollins]

FYI @emilymetcalf114 and @lzim

• [ ] The use of "X.X_versiontest*" term is to differentiate a version update, versus a more routine "test" update such as a minor model update.

Hi @hirenp-waferwire please refer to the teampsd_mtl_DEVOPS_architecture for instructions on this action. I am available for discussion and clarification. The image below is the diagram we are referring to.

[jamesmrollins]

@hirenp-waferwire I did not get a chance to test this today. I will test tomorrow 12/7

[lzim]

adjucicate_memo

How should this be handled to accurately track effort from Nov to Feb 2023? @jamesmrollins @emilymetcalf114 @epearman