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
On a self-hosted runner environment a lot of common tools are not available, such as the gh cli.
One workaround is to ensure an extra action that installs the gh before running the project-beta-automations action, but it would be nice for the action to test if the gh cli is present, and if not, download it from GitHub.
Below is the workaround we implemented in our org to allow the action to run in our self-hosted environment:
calexandre
changed the title
[Feature Request] Support for self-hosted runners, because gh client is not present
[Feature Request] Support for self-hosted runners, where gh client might not be present
Apr 13, 2022
@calexandre first of all, thank you for sharing your experience and solution for self-hosted runners. I must honestly admit that I have never tested with self-hosted runners, but it definitely makes sense that this tool is not installed. I will implement this as soon as possible and provide you with a solution.
On a
self-hosted
runner environment a lot of common tools are not available, such as thegh
cli.One workaround is to ensure an extra action that installs the
gh
before running theproject-beta-automations
action, but it would be nice for the action to test if thegh
cli is present, and if not, download it from GitHub.Below is the workaround we implemented in our org to allow the action to run in our self-hosted environment:
The text was updated successfully, but these errors were encountered: