| @@ -0,0 +1,2 @@ |
The one part of this I failed to appreciate initially is that for the public repositories we need to use the https://github.com links rather than the ssh ones using ssh into git@github.com. Some of the ssh links I was trying to pull from were failing to work and git also failed to report that which added to the agrivation. For those links a switch to using the ssh://git@ssh.github.com:443 link did work, but all of the SSH stuff requires that a user has the following set up properly. I have now switched the submodules in my bitweaver repository to use the https:// links. |
|
|
|
| @@ -21,2 +23,2 @@ |
| git config --global user.name "lsces"
|
| git config --global user.email "lester@lsces.co.uk"
|
| git config --global user.name "lsces" |
| git config --global user.email "lester@lsces.co.uk" |
|
|
| @@ -30,2 +32,2 @@ |
| ssh-keygen -t ed25519 -C "lester@lsces.co.uk"
|
| eval "$(ssh-agent -s)"
|
| ssh-keygen -t ed25519 -C "lester@lsces.co.uk" |
| eval "$(ssh-agent -s)" |
|
|
| @@ -41 +43 @@ |
| git remote set-url origin "https://lsces:github_pat_@github.com/lsces/bitweaver.git
|
| git remote set-url origin "https://lsces:github_pat_@github.com/lsces/bitweaver.git |
|
|
