-
Notifications
You must be signed in to change notification settings - Fork 255
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
Deployment key mapping not working with Julia's built-in Package Manager (Pkg) #98
Comments
Please see this comment: #99 (comment) I added at #99. It might help you to find out if this is a problem with your key setup or the tool ( Note that you don't have to put the repo name into the key comment if you don't want the key to be used for a particular repo only. If you have one key and it works in multiple (or all) repositories, just omit the key comment. That way, no mapping will be set up. |
This is probably about the Julia Language and its package manager: https://docs.julialang.org/en/v1/stdlib/Pkg/ |
@dongqiu93 Have you found a solution for this problem? Or maybe some workaround? |
Bumping to see if anybody else has a good workaround? |
Could you try setting the So, in your example, you would try something like this: - uses: webfactory/ssh-agent@v0.5.3
with:
ssh-private-key: |
${{ secrets.KEY1}}
${{ secrets.KEY2}}
- name: Test Pkg Add Pkg1
run: julia --project=docs/ -e 'using Pkg; Pkg.add(url="git@github.com:Org/Pkg1.jl.git");'
env:
JULIA_PKG_USE_CLI_GIT: 'true' |
The actions:
Configuring deployment key(s)
When simply running `git clone git@github.com:Org/Pkg1.jl.git" it would work, but when running Julia Pkg.add, it would fail:
It seems like the issue is with deploy-key mapping. Is there a way to stop this deploy-key mapping?
The text was updated successfully, but these errors were encountered: