Workflow

Cloning

rad clone z3Cqe7gEqxdqkGsPSS7KnBwJBBu5s

Let’s configure git for this cloned repository.

git config user.signingKey "$(rad self --ssh-key)"
git config gpg.ssh.allowedSignersFile .gitsigners

That way, I can keep my GPG key for non-Radicle repositories and other forges.

When I have to use GitHub to deploy or release code, I add a github remote for this specific case.

git remote add github git@github.com:Vexcited/Rikka.git

Note that you have to add the output of rad self --ssh-key to your GitHub SSH signing keys to have your commits verified with your Radicle SSH key.

# pull everything from radicle
git pull rad main

# push everything to github
git push github main

If you ever try to commit something and you get the following error.

error: Couldn't find key in agent?
fatal: failed to write commit object

That means your Radicle key is not in your ssh-agent, you can check this by running ssh-add -l.

Now, if you’re using Bitwarden, please look at my Bitwarden Guide for Radicle instead.

Otherwise, you can run rad auth to use Radicle’s SSH agent directly.

$ rad auth
✓ Passphrase: ******************
✓ Radicle key added to ssh-agent

You can check again ssh-add -l and you should see your Radicle key here now!