Is your feature request related to a problem? Please describe.
Running commands from a build-magic config file is useful, but doesn't integrate so well with CI/CD workflows/pipelines.
Describe the solution you'd like
Add an --export option that can convert a build-magic config file to aGitHub workflow file or GitLab CI file. Both formats support running arbitrary shell commands, so build-magic commands can map to commands in both formats easily. Build-magic stages can map to GitHub workflow steps and to GitLab CI stages or jobs. Command runners and environments cannot map deterministically so they should be ignored and the commands in the stages should be assumed to match the CI runner.
Is your feature request related to a problem? Please describe. Running commands from a build-magic config file is useful, but doesn't integrate so well with CI/CD workflows/pipelines.
Describe the solution you'd like Add an
--exportoption that can convert a build-magic config file to aGitHub workflow file or GitLab CI file. Both formats support running arbitrary shell commands, so build-magic commands can map to commands in both formats easily. Build-magic stages can map to GitHub workflow steps and to GitLab CI stages or jobs. Command runners and environments cannot map deterministically so they should be ignored and the commands in the stages should be assumed to match the CI runner.