Table of Contents

Github setup

Github (source forge) is not git (local-first distributed source control management software)! See Git for using git.

Github setup includes

  1. creating or finding an existing remote github repository url
    • avoid conflicting histories: dont generate a readme when creating a new repo
  2. syncing that with your files (on your computer, on rhea, on PSC, etc)
    • be sure you cd to the right directory before running git commands
  3. authenticating with github for git push permissions.
    • ssh keys recommended
    • ssh-keygen only once per user@server. don't run if existing ~/.ssh/id*.pub

New Repo

If you have an existing directory you want to put on github, DO NOT generate a readme when creating the github repository.

Existing Repo

Authentication

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

ssh keys

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

https app pass

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

1)
top right user iconsettingsssh and GPG keysnew ssh key