This page (revision-8) was last changed on 2021-04-10 22:40 by Murray Altheim

This page was created on 2021-03-17 07:58 by Murray Altheim

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
8 2021-04-10 22:40 4 KB Murray Altheim to previous
7 2021-04-01 09:36 4 KB Murray Altheim to previous | to last
6 2021-04-01 09:35 4 KB Murray Altheim to previous | to last
5 2021-03-17 20:45 3 KB Murray Altheim to previous | to last
4 2021-03-17 10:07 3 KB Murray Altheim to previous | to last
3 2021-03-17 08:41 3 KB Murray Altheim to previous | to last
2 2021-03-17 08:04 3 KB Murray Altheim to previous | to last
1 2021-03-17 07:58 2 KB Murray Altheim to last

Page References

Incoming links Outgoing links
How To Use Ssh Keys With Git Hub
HowToUseSshKeysWithGitHub

Version management

Difference between version and

At line 3 changed one line
This page contains notes on how I set up SSH keys to push and pull from my account on github. It's ''generally recommended'' that you read and follow their documentation (see the first link below) about how to set up either "personal access tokens" or SSH keys. These are __my notes__ about how I did it; I learned how from the github documentation.
This page contains notes on how I set up SSH keys to push and pull from my account on github. It's ''generally recommended'' that you read and follow their more extensive documentation (see the first __bold__ link below) about how to set up either "personal access tokens" or SSH keys. These are __my notes__ about how I did set up access using SSH keys; I learned how from the github documentation.
At line 6 changed one line
!! Steps
! A Typical Edit Session
At line 8 added 10 lines
# make some changes to files within a git project directory
# view the status of files with {{git status}}, maybe adding additional files with {{git add filename}}, or just add all updated files with {{git add -u}}
# commit the changes with {{git commit -m 'message describing the changes'}}
# push the changes to the repository with {{git push}}
If on that last step github asks your for username and password, that will stop working this coming August. You'll need to either use access tokens (e.g., OAuth) or SSH keys.
!!! Steps to Configuring SSH Keys
At line 30 added one line
At line 47 changed one line
! Try it Out
This will unfortunately need to be repeated upon each reboot. If you're using csh or tcsh as your shell you can add these two lines to your .cshrc file:
{{{
eval `ssh-agent`
ssh-add ~/.ssh/id_ed25519
}}}
At line 64 added 22 lines
If you're using bash you'd use the bash equivalents, to .bashrc.
{{{
eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519
}}}
! Set Username and Email Address
So that git knows who you are for a push, set your username:
{{{git config --global user.name "FIRST_NAME LAST_NAME"
}}}
...and set your email address:
{{{git config --global user.email "MY_NAME@example.com"
}}}
This isn't necessary if doing a clone on someone else's repository.
! Set URL Protocol to git: Rather than http:
At line 55 changed one line
If you see an http: protocol you should change the connection URL using:
If you see an {{http:}} protocol like below:
At line 94 added 6 lines
► git remote -v
origin https://github.com/[username]/[path] (fetch)
origin https://github.com/[username]/[path] (push)
}}}
you should change the connection URL to {{git:}} protocol using:
{{{
At line 102 added 4 lines
In the case of the NZPRG ros, this would be:
{{{
% git remote set-url origin git@github.com:ifurusato/ros.git
}}}
At line 107 added 2 lines
! Try It Out
At line 111 added one line
This page (revision-8) was last changed on 2021-04-10 22:40 by Murray AltheimTop