Difference between revisions of "HowTo SSH Keys"
Jump to navigation
Jump to search
Add public key to the destination repository (e.g.
Add private key to the source repository (
Line 24: | Line 24: | ||
# Click on "Secrets" and then on "Actions"<br />[[File:source_secrets.png]] | # Click on "Secrets" and then on "Actions"<br />[[File:source_secrets.png]] | ||
# Click on "New repository secret"<br />[[File:source_add_secret.png]] | # Click on "New repository secret"<br />[[File:source_add_secret.png]] | ||
# Enter a name (this name is used in the Github workflow): <code> | # Enter a name (this name is used in the Github workflow): <code>SSH_SYNC_KEY</code> | ||
# Paste the content of the <b>private key</b> into the "secret" text area<br />[[File:source_add_private_key.png]] | # Paste the content of the <b>private key</b> into the "secret" text area<br />[[File:source_add_private_key.png]] |
Latest revision as of 17:47, 2 April 2023
Generate and deploy SSH Keys to Github
Generate the keys
- Generate key
$ ssh-keygen -t ed25519 -C "your_email@example.com"
- Name the file
id_github_sigrokorg
and store it somewhere in your home directory (e.g./home/frank/.ssh
) - Don't enter a password
- You now have two files:
id_github_sigrokorg
(the private key) andid_github_sigrokorg.pub
(the public key)
Add public key to the destination repository (e.g. libsigrokflow
)
- Go the the Github page of the repository in question (e.g. https://github.com/sigrokproject/libsigrokflow)
- Click on "Settings" (repository settings)
- Click on "Deploy keys"
- Click on "Add deploy key"
- Enter a title, e.g. "Deploy key for sigrok-sync"
- Paste the content of the public key into the "key" text area
- Select "Allow write access"
Add private key to the source repository (sigrok-sync
)
- Go the the Github page of the
sigrok-sync
repository - Click on "Settings" (repository settings)
- Click on "Secrets" and then on "Actions"
- Click on "New repository secret"
- Enter a name (this name is used in the Github workflow):
SSH_SYNC_KEY
- Paste the content of the private key into the "secret" text area