[[1Password]] can manage SSH keys. Follow this [getting started guide](https://developer.1password.com/docs/ssh/get-started/) to configure 1Password. You need to repeat this process for each computer you set up.
Then navigate to your GitHub account, sign in if needed. In the upper-right corner of the page, click your profile photo then click **Settings**. In the "Access" section of the sidebar, click **SSH and GPG keys**. Click **New SSH key**. Use the 1Password web browser extension to generate and store your new SSH key.
You may need to configure commit signing before your first commit. In 1Password, navigate to the new SSH key you just created and click the three-dot menu in the top right corner and select **Configure Commit Signing**.
You can check that everything is working correctly with
```bash
ssh - T
[email protected]
```
You will be prompted for you passphrase (the same passphrase that unlocks 1Password). Note the characters will not show in the editor window.
Once everything is set up correctly, you should have a private key file in a `.ssh/` director in your home directory named something like `id_ed25519` that begins like
```
-----BEGIN OPENSSH PRIVATE KEY-----
...
```
Optionally, turn off the requirement to sign in each time you commit with
```bash
git config --global commit.gpgsign false
```
The full `.gitconfig` file (in your home directory) will look like:
```ini
[core]
editor = \"C:\\Users\\erikt\\AppData\\Local\\Programs\\Microsoft VS Code\\bin\\code\" --wait
sshCommand = C:/Windows/System32/OpenSSH/ssh.exe
[user]
email = <your email>
name = <your name>
signingkey = <your public key>
[gpg]
format = ssh
[gpg "ssh"]
program = "C:/Users/erikt/AppData/Local/1Password/app/8/op-ssh-sign.exe"
[commit]
gpgsign = false
```