[Slackbuilds-users] SBo-GitHub-Workflows.txt update suggestion

[Tim Dickson]

without setting up a key, the command

gitclone git at github:<username>/slackbuils.git

fails with the error

Cloning into 'slackbuilds'...
git at github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

(at least for me, YMMV)
regards, Tim

On 26/07/2024 03:45, Willy Sudiarto Raharjo wrote:
>> hi all, regarding https://slackbuilds.org/SBo-Github-Workflows.txt
>> A suggestion/request to help the git neophytes.
>>
>> it would be nice to add a point between 2 and 3 explaining how to 
>> create a certificate and upload it to you git account, otherwise 
>> point 3 onwards will fail. something like....
>>
>> if you haven't created a key for secure access, run
>> ssh-keygen -t ed25519 -C "your at email.address"
>> then
>> cat ~/.ssh/id_ed25519
>> copy the text of the catted file
>> in web-browser on github, click your profile icon (top left), click 
>> settings, under access (on the left) click SSH and GPG keys
>> click "New SSH key", add a title of your choice, and paste the copied 
>> key into the key text box, then click "Add SSH key"
>
> This is more of personal options you can have, but AFAIK, it's not 
> really necessary to do this in order to send PR to SBo
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com