I hope there is an author of the post. I appreciate sharing this example.
However, there is a caveat regarding the workflow code itself, that placing "run" statement with specific commands directly in YAML may make it difficult to debug locally. I would recommend that "run" statements be only for script execution and their number minimized. This way, scripts can be run locally without waiting for the entire CI pipeline to execute each time.
If there were a large number of contiguous commands that you could run in isolation, I’d agree. But it looks like four commands is the most you could chain together, and they depend on other tasks’ output, so I don’t see a lot of benefit to pulling them out into a shell script.
However, there is a caveat regarding the workflow code itself, that placing "run" statement with specific commands directly in YAML may make it difficult to debug locally. I would recommend that "run" statements be only for script execution and their number minimized. This way, scripts can be run locally without waiting for the entire CI pipeline to execute each time.