CI Errors: Permission denied (publickey) - fatal: Could not read from remote repository.
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 541
- Forks
- 185
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 4
Description
I'm trying to run CI for my PR: https://github.com/nodejs/node/pull/58461
and it keeps failing complaining that it doesn't have permissions to read the remote repository, more specifically:
21:08:09 + git remote prune origin
21:08:09 git@github.com: Permission denied (publickey).
21:08:09 fatal: Could not read from remote repository.
21:08:09
21:08:09 Please make sure you have the correct access rights
21:08:09 and the repository exists.
When running the CI I leave all the parameters to their defaults and I only set the safe check, PR id and commit SHA.
Could someone help me understand if I'm doing something wrong? 🙏 or is this some legitimate bug in the CI process?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked CI job node-test-commit/80374 and the reported git remote prune origin failure. Compare the default parameters with the supplied safe check, PR id, and commit SHA; done means identifying whether the permission failure is caused by the CI configuration or by the run parameters, with the next action documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100