Replies: 3 comments
-
I have a similar set up - private repo with private submodules. I was seeing the same error as you before adding a SSH key, I know you added a token, so maybe our errors are not related just in case, mine looks like this:
The ssh key is for a machine user with read only access. I'm sure you figured it out, but just in case or in case anyone else comes across this I though I would share. |
Beta Was this translation helpful? Give feedback.
-
I encountered a similar problem. I had set up my PAT correctly and my main repository could synchronize submodules correctly. However, all the checks in the pull request failed. That's my error when using actions/checkout@v4:
|
Beta Was this translation helpful? Give feedback.
-
For the moment the solution that worked for me was to make a clone of the public repository inside the organisation. |
Beta Was this translation helpful? Give feedback.
-
I do have a private organisation repository. Let's call it my_private_repo.
Inside this repository I do have a clone of a public repository from outside of organisation. Let's call it my_public_repo.
In my repository I do have the
.gitmodules
file:When I run the git submodule status command, the submodule appears.
In the YAML file I want to checkout the code and I use this scrtip:
When I try to run the workflow I encounter this message:
I search for similar problems and I tried several solutions, none worked.
For example I generated a token from my organisational account and add it to secrets and put it inside the checkout action. It didn't work.
I also tried to run the git command for update submodule. Same result.
If you know or have any idea on what else I can try, please let me know
Beta Was this translation helpful? Give feedback.
All reactions