-
Notifications
You must be signed in to change notification settings - Fork 259
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
Windows workflow fails with "Could not read from remote repository" #202
Comments
It's because of recursive submodules, see #130 (comment) The workaround is to use the checkout action, init submodules manually, use this action, clone submodules manually. |
I also having the same issue on Windows without name: Development Build
on:
push:
branches:
- dev
pull_request:
branches:
- dev
env:
CARGO_NET_GIT_FETCH_WITH_CLI: true
concurrency: ${{ github.ref }}
permissions:
contents: read
id-token: write
jobs:
windows:
name: Build (Windows)
runs-on: windows-latest
steps:
- name: Checkout source
uses: actions/checkout@v4
- name: Set up SSH agent
uses: webfactory/[email protected]
with:
ssh-private-key: ${{ secrets.REDACED }} The error:
|
@sykhro thanks for your suggestion. It's still not working for me on Windows though. I now have the following workflow (again some bits are redacted):
(Same results with checkout@v3 and [email protected].) Full log of the submodule step:
Looks like it's the same problem as @ultimaweapon EDIT: replacing |
We have the same issue, changing |
I was reading the code, and i think the problem is the "homeSsh" variable which have the the root concat with /.ssh, but on windows path use "" instead of "/" so the ssh-agent are not finding the keys |
Is there any update or fix in sight? I am stuck with version |
Linked to #221 |
My Github action succeeds on Linux but fails on Windows the error:
Full log:
My workflow file (with some bits redacted):
I also want to note I really like this tool! I am not entirely sure how well Windows is supported and if this should work at all.
Thanks.
The text was updated successfully, but these errors were encountered: