I have a trio of internal repositories in my organization.
In the package.json of Repository A is a dependency on the contents of Repository B. Repository C is just like B.
When I run yarn or npm locally, I have no problems with the installation of the dependencies.
However when I trigger a workflow that is intended to install dependencies then do a build, the process fails.
The output looks like this:
yarn install v1.22.0 [1/4] Resolving packages... error Command failed. Exit code: 128 Command: git Arguments: ls-remote --tags --heads ***github.com/<myorg>/<RepositoryB>.git Directory: /github/workspace Output: remote: Repository not found. fatal: repository 'https://github.com/<myorg>/<RepositoryB>.git/' not found info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
I have tried several approaches to fixing this including using a PAT with Secrets on Repository A. That PAT was given all permissions except for creating GPG keys, and Org Admin. I have also tried using SSH Key and putting the private key in Repository A Secrets and the deploy key in Repository B.
This seems like a big missing feature of Actions if there is no way to accomplish.