Authentication

OpenCommit supports Git operations over SSH and HTTPS.

For regular development, we strongly recommend using SSH keys. SSH is secure, convenient, and avoids repeated password prompts.

If you use HTTPS, you need an access token when pushing changes, because OpenCommit requires two-factor authentication (2FA) for all accounts.

SSH Keys (Recommended)#

SSH keys allow your computer to authenticate with OpenCommit without using your account password.

Step 1 – Check for an existing SSH key#

Open a terminal and run:

ls -al ~/.ssh

Look for a public key file such as id_ed25519.pub.

If you already have one, you can use it. If not, create a new one.

Step 2 – Create a new SSH key#

ssh-keygen -t ed25519 -C "your_email@example.com"

When prompted:

• Press Enter to accept the default file location
• Optionally set a passphrase

This creates:

• ~/.ssh/id_ed25519 – your private key
• ~/.ssh/id_ed25519.pub – your public key

Never share your private key. Only upload the .pub public key to OpenCommit.

Step 3 – Copy your public key#

Linux#

cat ~/.ssh/id_ed25519.pub

Copy the full output.

macOS#

pbcopy < ~/.ssh/id_ed25519.pub

Windows PowerShell#

Get-Content ~/.ssh/id_ed25519.pub | Set-Clipboard

Step 4 – Add the key to OpenCommit#

1. Go to Settings → SSH / GPG Keys
2. Click Add key
3. Give the key a descriptive name, such as Work laptop
4. Paste your public key
5. Click Add key

Step 5 – Test your SSH connection#

ssh -T git@opencommit.eu

If the connection works, OpenCommit should confirm that you authenticated successfully. This command does not open a shell session; it only tests authentication.

✅ Done#

HTTPS with Access Tokens#

You can clone public repositories over HTTPS without additional setup:

git clone https://opencommit.eu/YOUR_USERNAME/REPOSITORY.git

Private repositories require authentication.

To push changes over HTTPS, use an access token instead of your account password.

Step 1 – Create an access token#

1. Go to Settings → Applications
2. Find the Access Tokens panel
3. Click New access token
4. Enter a name, such as Git HTTPS
5. Select the repository permissions needed for the repositories you want to access
6. Click Generate Token
7. Copy the token immediately

You will only see the token once. Store it somewhere safe, such as a password manager.

Step 2 – Push using HTTPS#

When Git asks for credentials:

• Username: your OpenCommit username
• Password: your access token

Example:

git push origin main

Git may prompt:

Username for 'https://opencommit.eu': YOUR_USERNAME
Password for 'https://YOUR_USERNAME@opencommit.eu': YOUR_ACCESS_TOKEN

Because OpenCommit requires 2FA, your account password cannot be used for HTTPS pushes. Always use an access token instead.

✅ Done#

Which should I use?#

Use SSH if you work from your own computer.

Use HTTPS with an access token if:

• You cannot use SSH
• You are working in an environment where HTTPS is required
• You are following tooling that expects HTTPS repository URLs

What’s next?#

• Continue with the Quickstart to create your first repository & push your first commit