You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering what is the story like with GitHub-hosted runners. The current instructions require patching the runner, but this is done on disk prior to launch and is only feasible for self-hosted runners, but with GitHub-hosted runners, any steps that are run inside of a workflow are with an already running runner?
This might require patching the runner in memory - has anyone attempted this before?
The text was updated successfully, but these errors were encountered:
I was wondering what is the story like with GitHub-hosted runners. The current instructions require patching the runner, but this is done on disk prior to launch and is only feasible for self-hosted runners, but with GitHub-hosted runners, any steps that are run inside of a workflow are with an already running runner?
This might require patching the runner in memory - has anyone attempted this before?
The text was updated successfully, but these errors were encountered: