-
Notifications
You must be signed in to change notification settings - Fork 5
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
Refactor workflows #92
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@YewoMhango how do we fix this issue
I replaced it with this |
Oh, okay, I see. For me, I also encountered that error and it somehow got fixed when I ran |
This fixed the build, we can publish our own package later. I plan to move this repo to the main organization here https://github.com/SparkEdUAB this way it can be together with other repository. |
I actually wanted to suggest that we use an Adobe package. It's good I
have used it before
…On Sat, 20 Apr 2024, 20:36 Olivier JM Maniraho, ***@***.***> wrote:
@YewoMhango <https://github.com/YewoMhango> how do we fix this issue
yarn install v1.22.19
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
error Command failed.
Exit code: 128
Command: git
Arguments: ls-remote --tags --heads ***@***.***/YewoMhango/react-pdf-viewer.git
Directory: /Users/olivierjm/sparked-next
***@***.***: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
I replaced it with this ***@***.***/react-pdf": "
https://github.com/YewoMhango/react-pdf-viewer.git", but still got the
error.
—
Reply to this email directly, view it on GitHub
<#92 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABCPXPO2UQ5S6XW43CRTUSLY6KYRVAVCNFSM6AAAAABGQV4PQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRXG42TCNZYGQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Okay, great |
That seems like it would be very helpful |
No description provided.