Add to documentation if runners are "throw away" / "single use"

[mithro]

This project looks super interesting but I had one question, are the runners thrown away after they run a single job?

According to https://docs.github.com/en/free-pro-team@latest/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories;

We recommend that you do not use self-hosted runners with public repositories.

Forks of your public repository can potentially run dangerous code on your self-hosted runner machine by creating a pull request that executes the code in a workflow.

This is not an issue with GitHub-hosted runners because each GitHub-hosted runner is always a clean isolated virtual machine, and it is destroyed at the end of the job execution.

It would be good if the documentation explicitly stated if it behaves (or can be configured to behave) like the GitHub-hosted runners were the runner is thrown away after a single use.

Thanks for your awesome work!

[davidkarlsen]

See actions/runner#510 for this feature.
You can try enabling it with an env-var like:

- name: ACTIONS_RUNNER_INPUT_ONCE
  value: "true"

[davidkarlsen]

@mithro did it work out for you?

[mithro]

@davidkarlsen - Haven't had a chance to test it yet. Probably be a week or two before we get it going.

[davidkarlsen]

No feedback - closing. Feel free to reopen if needed.

[heilerich]

The solution suggested in @davidkarlsen 's comment works perfectly for me.

I can't reopen this issue, but I think this should go into the documentation somewhere.

Great project!