-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem cloning repositories on self hosted runners #16
Comments
@derberg what do you think of this solution? https://github.com/Tjitse-E/global-workflows-support/commit/65bcc73644877b8e9e94ad8e25026c18fd4c29a3. Using the github token to clone the repo via HTTPS works for me. |
@Tjitse-E sounds good, I never thought about using it on private repos, but of course it makes sense 😄 Just solution should be provided in different place. The |
Ok, I will see if I have some time to create a PR for this in the coming days. |
@Tjitse-E this is not supported with 0.3.0 https://github.com/derberg/global-workflows-support/releases/tag/v0.3.0 |
Describe the bug
I'm having problems with the Github authentication, the clone action doesn't work:
I traced the problem back to steveukx/git-js#594, altough there the issue was caused by
actions/checkout@v1
. I'm usingactions/checkout@v2
.How to Reproduce
I'm using private repositories, so I cannot specify the steps to reproduce. Probably it has something to do with my self hosted runner setup.
The text was updated successfully, but these errors were encountered: