Skip to main content
Signing your commits verifies that you are the author of a change and prevents commit spoofing. This guide sets up SSH key-based signing in the Paradime IDE so every new commit in your repository is signed automatically.
Prerequisites
  • Paradime IDE access.
  • A git repository initialized in your Paradime workspace (connect a repository).
  • A GitHub account, to add your signing key.
Estimated time: 5 minutes.

Steps

1

Create the setup script

In the Paradime IDE, create a new file called setup_git_signed_commits.sh with the following content:
2

Make the script executable

Open the Paradime terminal and run:
3

Run the setup script

Execute the script:
When prompted, enter a comment for your key (typically your name and email address).
4

Add your signing key to GitHub

  1. Copy the public key printed in the terminal output.
  2. Go to your GitHub account settings: https://github.com/settings/keys.
  3. Click New SSH key.
  4. Choose Signing Key as the key type.
  5. Paste your public key in the provided field.
  6. Give your key a descriptive title.
  7. Click Add SSH key.
You must choose the Signing Key type. An SSH key added as an authentication key will not mark your commits as verified.
Every new commit you make in this repository is now signed automatically. View a new commit on GitHub and confirm it shows a Verified badge. If it does not, recheck that the key was added with the Signing Key type in step 4.

Next steps

Protect the main branch

Require pull requests and reviews before merging to main.

Explore Git history with GitLens

Inspect authorship and history in the Code IDE.

Connect a GitHub repository

Set up your repository connection in Paradime.

Version control in the Code IDE

How commits, branches, and pushes work in Paradime.