Yusuke Miyazaki

Hi @imphil, thanks for filing a ticket. This is actually an expected behavior of the current tox-gh-actions. In short, how tox-gh-actions works is 1. Get list of environment candidates from...

> I understand the current behavior, but I'm wondering if it couldn't be changed? Is there a reason why only listed environments can be used in gh-actions? Sure, I can...

Hello everyone, thanks for the feedback. At this point, I'd like to avoid actually failing the tox when it couldn't find no environments as it can be technically a breaking...

Thanks for sharing additional feedback. Adding an option to fail should be possible but let me think about it a bit deeper before actually implementing it as tox-gh-actions hasn't provided...

It seems GitHub Actions doesn't provide a platform type via environment variables: https://help.github.com/en/actions/configuring-and-managing-workflows/using-environment-variables#default-environment-variables So, it's difficult to detect it from the plugin side. We probably need to use #20 and...

Sorry for the slow response. I'm not sure if there's an API we can split the steps from the code executed by GitHub Actions.

This situation has improved slightly in #36. We now groups logs from each environment using GitHub Actions' feature.

https://github.com/ymyzk/tox-gh-actions/releases/tag/v3.0.0 is released.

Sorry for a slow response but I just published tox-gh-actions v2.12.0 which adds an option to fail when no environments are matched. Please check details in README and give it...

@intgr It should be available on mypy Playground now: https://github.com/ymyzk/mypy-playground/pull/388