Is your feature request related to a problem? Please describe.
A stage intended to run on Windows cannot run on Linux or MacOS. For this reason, it would be useful to be able to tag a stage with the intended OS.
Describe the solution you'd like
Since the environment: field isn't used for the Local command runner, this can optionally be used to identify which OS the runner is intended for. Options should include "windows" and "macos" or "darwin". Individual Linux distros should also be included such as "debian", "centos", and "arch". The use would be optional and if provided, a check for the operating system is run at the beginning of the stage to determine the OS. If an exit code of 0 is returned, continue with executing the stage. Otherwise, skip the stage and notify the user.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe. A stage intended to run on Windows cannot run on Linux or MacOS. For this reason, it would be useful to be able to tag a stage with the intended OS.
Describe the solution you'd like Since the
environment:field isn't used for the Local command runner, this can optionally be used to identify which OS the runner is intended for. Options should include "windows" and "macos" or "darwin". Individual Linux distros should also be included such as "debian", "centos", and "arch". The use would be optional and if provided, a check for the operating system is run at the beginning of the stage to determine the OS. If an exit code of 0 is returned, continue with executing the stage. Otherwise, skip the stage and notify the user.Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.