Thanks to me fiddling with LN. Nodes over the years I am familiar with SSH just need to remember how to establish a token 

BlokchainB

deleted my other comment because of formatting issues and my edit timer ran out:

Learning to code has been extremely lonely journey for me .

It’s nice to have someone to chat with and talk out the issues. It keeps me motivated and engaged and not pushing this off.

This is a super common Git authentication issue! I have to do some googling everytime I go through this process myself, it's kind of annoying...

But I just realized since it's an authentication problem, using SSH instead of HTTP might help (not sure if mentioning SSH will confuse you even more; I hope not).

Additionally, I noticed SN swallowed some text in the instructions 

devs

Learning to code: My MVP as inspired by PlebDev

_deleted my other comment because of formatting issues and my edit timer ran out:_

> Learning to code has been extremely lonely journey for me .
>
> It’s nice to have someone to chat with and talk out the issues. It keeps me motivated and engaged and not pushing this off.

Joining the [plebdevs discord](https://discord.com/invite/t8DCMcq39d) might help you if you haven't already.

btw, I can only cosign what @bitcoinplebdev mentioned here:

> This is a super common Git authentication issue! I have to do some googling everytime I go through this process myself, it's kind of annoying...

But I just realized since it's an authentication problem, using SSH instead of HTTP might help (not sure if mentioning SSH will confuse you even more; I hope not).

So instead of `https://github.com/ekzyis/repo`, I use `git@github.com:ekzyis/repo` after I [added my SSH public key to my Github account](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account) (which I only had to do once).

**Additionally, I noticed SN swallowed some text in the instructions @bitcoinplebdev gave you, see https://stacker.news/items/881887?commentId=884050**