Different environment depending on OS?

[samwaseda]

I'm not sure if I'm posting the issue in the right place, but it is there a way to exclude certain packages depending on the OS? In particular it's about this PR and I have to exclude cwl when it's windows.

[liamhuber]

I'm afraid the push-pull.yml re-usable action doesn't easily allow for this. The main testing is a sparse matrix across python versions and runners (OSs), where all python versions get run on the main runner, and all runners get run on the main python version -- but all of these use the same environment file. There is alternate-tests-env-files, the presence of which allows you to trigger tests for some other env. But the intent of that is to cover the lower-bounds, and so is already used up in semantikon.

However, what you can do is just add another job into the workflow that triggers push-pull.yml. We do exactly this in flowrep, and for the same purpose of generating a different env -- in this case, one without the optional dependencies. I recommend following exactly this pattern. Manually set runner-alt1 when triggering push-pull so you avoid windows, and then add a separate job below it like in flowrep, but specify runner to be "windows-latest". Honestly, the tests-and-coverage reusable workflow is probably slightly overkill, you could probably build a job more tightly by using the unit-tests action directly, but it would take a bit more writing -- the reusable action is just the action tag and a few input flags set.