Provide description of requirements for running Unity CI actions on a self-hosted runner

Is your feature request related to a problem? Please describe. Currently afaik Windows and other OSs are unsupported so I can’t use a self-hosted runner without knowing about the capabilities expected by this action (or I need to install Ubuntu beside Windows on my system which may be undesirable unless the GitHub self-hosted runner application works through WSL, which is harder to set up than on a Linux distro which supports systemd).

Describe the solution you’d like A description page which provides clear information on what configuration is expected from a machine which shall run this action.

Describe alternatives you’ve considered The only other alternative is to go into the repo and dive into the code to find what capabilities are expected.

Additional context When I first tried running the Activation action using windows-latest I was greeted with an error which read something like win32 is not supported.

[webbertakken]

Thank you @Vivraan for this valuable feedback.

I agree we should add a section about self-hosted runners, and expected capabilities, which simply put is ubuntu, and the configuration the same as default runners. What other information would you expect to find on this page?

I think the biggest problem with Windows specifically would be doubling the code for things like file paths and other OS specific things. In practice it wouldn’t be too hard to support Windows at all, as the action is mostly a bootstrapper that mounts a container.

Looking forward to hear your thoughts on this.

[Vivraan]

Perhaps a clarifying link to the config of default runners would suffice.

Found this from the logs form GitHub Actions: https://github.com/actions/virtual-environments/blob/ubuntu18/20200920.1/images/linux/Ubuntu1804-README.md