...

...

HTTPS with a Personal Access Token

https://docs.github.com/en/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions https://docs.github.com/en/actions/using-jobs/running-jobs-in-a-container#example-defining-credentials-for-a-container-registry

I have only tested with the most simple use case - publishing containers for that repo only (which is what the example in the preceding link shows).

...

Use the default provided ${{ secrets.GITHUB_TOKEN }} provided when you run an action on your repo

...

...

Dual Work-Personal SSH Accounts

Nothing changes for your personal account (assuming it already exists)

For your work account:

1. Create an ssh key and save it to a named file

# This creates ~/.ssh/work_rsa and ~/.ssh/work_rsa.pub
$ ssh-keygen -t rsa -C "bob-work@gmail.com" -f "work"

2. Upload the ssh key to your github work account

3. Create a new github.com configuration in ~/.ssh/config

Host work
    Hostname github.com
    User git
    IdentityFile ~/.ssh/work

4. Test the ssh key

$ ssh -T git@github.com
Hi bob! You've successfully authenticated, but GitHub does not provide shell access.
$ ssh -T git@work
Hi bob-work! You've successfully authenticated, but GitHub does not provide shell access.

5. Clone

$ git clone git@github.com:bob/my_open_source_repo.git
$ git clone git@work:mercury/thirteenth-floor.git