Add markdown regeneration to the rules transform task
jpower432 opened this issue · comments
Is your feature request related to a problem? Please describe.
If the rules-transform action is run, the autosync action with assembly skipped needs to be to propagate those changes to the markdown. If this is not done, the OSCAL JSON will be overwritten. If these tasks need to be run in order for the workflow to function properly, they should exist in the same action to reduce the possibility of error and eliminate the need to build the image twice for a single operation.
Describe the solution you'd like
Add the RegenerateTask to the rules-transform under entrypoints.
Describe alternatives you've considered
The current option - But you would need to build, commit, and push twice if there are resulting markdown changes.
Additional context
Demo repo
cc @gvauter