Skip to content
Discussion options

You must be logged in to vote

Thanks for the heads up — I've already spotted the issue. The problem is that the repository was created as a fork of a public repo, and GitHub disables self-hosted runners on public repositories for security reasons. That's why the action gets stuck in the queue indefinitely.

The fix involves migrating the repository to a new private one, which will allow the self-hosted runner to work properly. I'll take care of it this afternoon.

Just a heads up: if you happen to do a push or pull while I'm doing the migration, you might get a temporary error. Don't worry about it — it'll be short-lived. I'll let you know here once everything is sorted out. You won't need to do anything on your end onc…

Replies: 1 comment 5 replies

Comment options

You must be logged in to vote
5 replies
@TheAlbertDev
Comment options

@loreamazquiaran
Comment options

@TheAlbertDev
Comment options

@loreamazquiaran
Comment options

@TheAlbertDev
Comment options

Answer selected by TheAlbertDev
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants