top right user icon→settings→ssh and GPG keys → new ssh key
Github (source forge) is not git (local-first distributed source control management software)! See Git for using git.
Github setup includes
cd to the right directory before running git commandsgit push permissions. ssh-keygen only once per user@server. don't run if existing ~/.ssh/id*.pubIf you have an existing directory you want to put on github, DO NOT generate a readme when creating the github repository.
http://github.com/new or Home > green new repo
Follow the instructions github provides be sure to cd into the code directory before running git commands cd my-exsiting-data/ # go to the directory of your existing code git remote add origin git@github.com:$USER/$REPONAME git push -u origin main
<> Code button > Local Tab > SSH header.git clone git@github.com/$USER/$REPO
For git push to github, you'll need some way to confirm your credentials. Authentication can happen with ssh keys (recommended) or an app password
git push can use ssh authentication unique to a user and computer pair. You need a key likely in ~/.ssh/id_ed25519.pub.
Contents of ~/.ssh/id_ed25519.pub should be pasted into new ssh key modal on https://github.com/settings/keys 1)
cat ~/.ssh/id_ed25519.pub
If ~/.ssh/id_ed25519.pub doesn't exist, ssh-keygen can make it (use empty password for convenience. hit enter at password prompt to leave blank). See more documentaiton on github
ssh-keygen only needs to be run once per user per computer. Do not rerun if any ~/.ssh/id*.pub file exists – you risk deleting your key
To push to https (vs ssh like git@) repos, you'll need to use a personal authentication token when prompted for a password. See github's documentation
top right user icon→settings→ssh and GPG keys → new ssh key