Documentation

Creating an Account

Mon, 01 Jan 0001 00:00:00 +0000

Pre-flight check:
OpenCommit requires two-factor authentication (2FA) for all accounts.

Step 1 – Register#

Go to OpenCommit
Click Register
Fill in:
- Username
- Email address
- Password
Click Register account

Required Agreement
By creating an account, you agree to:

The Terms of Service and Privacy Policy

Follow the Code of Conduct in all interactions

Use the platform responsibly and ethically

Accept that the service is provided “as is” without warranties

Step 2 – Verify your email#

After registering:

Introduction

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Introduction to Actions

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Repositories

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Two-Factor Authentication

Mon, 01 Jan 0001 00:00:00 +0000

Two-Factor Authentication (2FA) adds an additional layer of security to your account by requiring a second form of verification in addition to your password. OpenCommit supports Time-based One-Time Passwords (TOTP) and hardware security keys.

Enabling 2FA is required for all users by OpenCommit.

Supported Methods#

OpenCommit supports the following 2FA methods:

TOTP (Authenticator Apps)
Use an app such as:
- Aegis
- Google Authenticator
- Microsoft Authenticator
- Authy
Hardware Security Keys (WebAuthn/FIDO2)
Examples include:

What is Git?

Mon, 01 Jan 0001 00:00:00 +0000

OpenCommit is a platform for hosting Git repositories. If you are new to development, here is the short version of what that means.

Git vs. OpenCommit#

It is important to understand the difference between the tool and the service:

Git is the software that runs on your computer. It tracks the history of your files, allows you to “undo” changes, and manage different versions of your work.
OpenCommit is the hosting service (the “Forge”). It provides a place to store your Git repositories online, collaborate with others via Pull Requests, track bugs via Issues, and automate tasks with Actions.

Analogy: Git is like your word processor; OpenCommit is like a collaborative cloud drive where you share your documents.

Installation

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Installing Git

Mon, 01 Jan 0001 00:00:00 +0000

Step 1 – Install Git#

macOS

brew install git

Linux

# Debian / Ubuntu
sudo apt update && sudo apt install git

# Fedora / RHEL
sudo dnf install git

# Arch
sudo pacman -S git

Windows
Download the installer from git-scm.com. We recommend using Git Bash for all subsequent commands.

Step 2 – Configure Your Identity#

Git requires a name and email to attribute your work. Run these commands in your terminal:

Issues

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Quickstart (2 mins)

Mon, 01 Jan 0001 00:00:00 +0000

Pre-flight check:
This guide assumes you have an OpenCommit account and are logged in. It also assumes you already have Git installed locally.

→ See Creating an Account
→ See Installing Git

Prefer the command line? → See CLI Quickstart

Step 1 – Create a repository#

Click the “+” (Create) button in the top navigation
Select “New Repository”
Choose a name (e.g. my-first-repo)
Click Create Repository

Step 2 – Clone the repository#

We strongly recommend using SSH → See Authentication for setting it up.

Quickstart Workflow

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Authentication

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Authentication

Mon, 01 Jan 0001 00:00:00 +0000

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:

Connecting via SSH

Mon, 01 Jan 0001 00:00:00 +0000

Unlike the Getting Started guide, this page provides a deeper reference for using SSH with Git, including key management, configuration, commit signing, and security best practices.

SSH and Git#

SSH is used by Git for secure, passwordless authentication when interacting with remote repositories. Instead of passwords, SSH relies on asymmetric key pairs:

Private key — stored securely on your machine, never shared
Public key — added to your OpenCommit account

When you connect, your client proves possession of the private key without ever transmitting it. This is fundamentally more secure than password-based authentication.

Migration Guide

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Pull Requests

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Branches and Tags

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Connecting via HTTPS

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Migrating from GitHub

Mon, 01 Jan 0001 00:00:00 +0000

OpenCommit can migrate existing repositories from GitHub.

A migration can copy the Git repository itself, including branches and commit history. Depending on the source repository and the permissions you provide, it may also migrate metadata such as issues, pull requests, labels, milestones, releases, and wiki pages.

Tip:
This page is geared towards GitHub but migrating from other services can be achieved in a similar fashion.

What can be migrated?#

When migrating from GitHub, OpenCommit can import:

Quickstart

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Usage and Limits

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Common Commands

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Common Commands

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Organizations

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

GitHub CLI Migration

Mon, 01 Jan 0001 00:00:00 +0000

This page intentionally left blank.

We're working on it...

Brand Guidelines

Mon, 01 Jan 0001 00:00:00 +0000

Thank you for your interest in representing OpenCommit! These guidelines and assets are provided to help you use our brand correctly when linking to your profile, mentioning us in articles, or integrating with our platform.

The Logo#

Our logo is the primary identifier of OpenCommit. We provide it in two main formats: the Full Wordmark (Icon + Text) and the Icon Only.

Assets to Provide:#

Logo Pack (.zip): Download all assets
SVG (Vector): Icon | Full Wordmark
PNG (Transparent): Icon | Full Wordmark

Version Usage:#

Preferred version: We prefer users to use the colour or colour-edged versions of assets at all times.
Positive (Colour/Dark): Use on white or light-coloured backgrounds.
Negative (Colour-Edged/White): Use on dark backgrounds or photography.
Icon Only: Best for social link bars, favicons, or small UI elements where space is limited.

Name Usage#

Consistency in how our name is written helps build brand recognition.

Contact

Mon, 01 Jan 0001 00:00:00 +0000

Stay up to date#

We can follow us on Mastodon or keep track by reading our blog.

Questions and Issues#

Just like other public, non-commercial and open forges, OpenCommit relies on our community members helping each other via public spaces. This is an always-available and reliable way to get help for most issues.

Usually there will be other people who have experience in the area or had similar problems in the past and can participate in helping you out. You can use these spaces to provide support to others too.

Two-Factor Authentication

Fri, 06 Feb 2026 00:00:00 +0000

The Context#

OpenCommit is a code hosting platform. That means accounts are not just profiles, they are keys.

Keys to:

repositories,
releases,
issue trackers,
project roadmaps,
CI tokens and integrations,
maintainership, trust, and reputation.

In the broader ecosystem, account takeovers are one of the most common ways projects get compromised. Sometimes it’s dramatic (malicious releases, backdoors). Often it’s mundane (spam, credential stuffing or opportunistic abuse for example). Either way, the impact isn’t contained to one person. When an account is compromised, communities lose time, users lose trust, and maintainers lose sleep.

Using Names Fairly

Sun, 14 Dec 2025 00:00:00 +0000

The Context#

If you see forgejo/forgejo or mozilla/firefox, you immediately assume you’re looking at the “real” project, or at least something closely related. Names carry trust, history, and expectations.

But most platforms work on a simple rule: first come, first served.

That works well until it doesn’t. A random account grabs a well‑known project name, does nothing with it, and suddenly the actual maintainers have to beg, negotiate, or move to an awkward alternative spelling. Users get confused. Search results look sketchy. People waste time figuring out what’s “official” and what isn’t.

Artificial Intelligence

Mon, 24 Nov 2025 00:00:00 +0000

The Context#

AI, and especially LLMs like ChatGPT, are just about everywhere nowadays. Companies are integrating LLMs into things where many people don’t need or even want it. All those LLMs also need to be fed training data.

Public Open Source repositories like those on Github are a prime candidate.

How We Think About This#

While the OpenCommit Foundation acknowledges the many benefits brought by AI in general and in software development in particular, we also see the many negative sides and its pitfalls.

Mon, 01 Jan 0001 00:00:00 +0000

Code of Conduct — OpenCommit#

Effective Date: 2026-01-31
Last Updated: 2026-03-25

1. Purpose#

OpenCommit exists to support open source development and responsible software collaboration. This Code of Conduct defines the standards of behavior expected from all users of the OpenCommit platform (the “Service”).

Our goal is to foster a stable, inclusive, professional, and non-abusive environment for developers, organizations, and contributors.

This Code of Conduct applies to:

All users of the OpenCommit platform
All public and private repositories hosted on the Service
Issues, pull/merge requests, comments, profiles, and other user-generated content
Communications that take place through the platform

Violation of this Code may result in enforcement actions as described below.

Mon, 01 Jan 0001 00:00:00 +0000

Data Processing Addendum (DPA) — OpenCommit#

Effective Date: 2026-01-31
Last Updated: 2026-04-04

This Data Processing Addendum (“DPA”) forms part of the Terms of Service (“Agreement”) between Stichting OpenGit, operating as OpenCommit (OpenCommit Foundation), (“Processor”) and the entity subscribing to the Service (“Controller”).

1. Definitions#

“Data Protection Laws” means the EU General Data Protection Regulation (GDPR) and the Dutch GDPR Implementation Act (UAVG).
“Personal Data” means any information relating to an identified or identifiable natural person processed by Processor on behalf of Controller within the Service.
“Sub-processor” means any third party appointed by Processor to process Personal Data.

2. Scope and Role#

This DPA applies where OpenCommit processes Personal Data as a Processor on behalf of the Controller in the course of providing git hosting services. This typically includes data contained within private repositories, issue trackers, and pull requests.

Mon, 01 Jan 0001 00:00:00 +0000

Privacy Policy — OpenCommit#

Effective Date: 2026-01-31
Last Updated: 2026-04-04

The OpenCommit Foundation (Stichting OpenGit, a foundation (stichting)) (“OpenCommit”, “we”, “us”, or “our”) is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our git hosting service at opencommit.eu (the “Service”).

OpenCommit is a foundation established in the Netherlands and is subject to the General Data Protection Regulation (GDPR).

Mon, 01 Jan 0001 00:00:00 +0000

Security Overview — OpenCommit#

Last Updated: 2026-04-04

OpenCommit aims to protect the confidentiality, integrity, and availability of the Service and user data. This Security Overview describes the technical and organizational measures we use to secure the platform. It is provided for transparency and does not form part of the Terms of Service.

1. Infrastructure and Hosting#

EEA-based hosting: Core infrastructure is hosted within the European Economic Area (EEA).
Hosting provider: Infrastructure is hosted with Hetzner Online GmbH in Germany and Finland.
Data center security: We rely on Hetzner’s data center security controls and certifications (including ISO/IEC 27001 where applicable) and industry-standard physical security measures.

2. Network Security#

Segmentation: We segment services to limit unnecessary access between components.
Firewalls: Inbound access is restricted to required ports and services.
Administrative access: Administrative access is limited and protected using strong authentication and encrypted connections.

3. Encryption#

In transit: Traffic between clients (web browsers and git clients) and OpenCommit is encrypted using modern TLS.
At rest: We use encryption where appropriate for backups and sensitive configuration material.

4. Authentication and Account Security#

Passwords: Passwords are stored using strong, one-way hashing.
2FA: We support and may require two-factor authentication (2FA) for accounts or organizations.
SSH: Git access supports SSH keys; users are encouraged to use modern key types (e.g., Ed25519).

5. Application and Dependency Security#

Forge software: The Service is based on Forgejo.
Patching: We monitor upstream security advisories and apply relevant security updates in a timely manner.
Hardening: We aim to minimize the attack surface by disabling or restricting non-essential services and features.

6. Monitoring and Logging#

Operational monitoring: We monitor service health and availability to detect incidents and outages.
Status monitoring: We may use third parties (e.g., Uptime Robot) for status/availability checks.
Security logging: We maintain logs relevant to security and abuse prevention. Access to logs is restricted.

7. Backups and Recovery#

Backups: We perform regular backups of repository and database data.
Recovery: We maintain recovery procedures to restore service after incidents.
User responsibility: Users remain responsible for maintaining independent backups of their repositories.

8. Incident Response#

Response: We investigate suspected security incidents and take appropriate steps to contain and remediate issues.
Notification: Where required by law or contract (for example under a DPA), we will notify affected parties of relevant incidents.

9. Vulnerability Reporting#

If you believe you have found a security vulnerability in OpenCommit, please contact:

SSH Host Key Fingerprints

Mon, 01 Jan 0001 00:00:00 +0000

Fingerprints last updated: 2026-05-10

OpenCommit supports multiple SSH host key algorithms. When connecting for the first time, your SSH client will ask you to verify the server’s fingerprint.

Compare it against the values below before accepting.

Algorithm	Bits	Fingerprint
ED25519 *)	256	`SHA256:4Wrv0Q0gJL4eBXT1HD3tO06OBOpzRfeRK1di5f0eKE8`
ECDSA	256	`SHA256:VNxFvF4zfPcWzJD81BK2jwMEDpC+DWv3PmvZ/3VhcA4`
RSA	4096	`SHA256:XlsftfyASOW1F9hGwmGcgy8j0skZVs1JZXXmJ+M6Cek`

*) recommended algorithm

If the fingerprint does not match, do not accept the connection.
This may indicate a misconfiguration or a man-in-the-middle attack. Please open an issue.

Mon, 01 Jan 0001 00:00:00 +0000

Sub-processors — OpenCommit#

Last Updated: 2026-04-04

To provide our Service, OpenCommit engages the following third-party sub-processors to perform specific processing activities. All sub-processors are bound by Data Processing Agreements (DPAs) to ensure the protection of your personal data.

Entity	Activity	Location
Hetzner Online GmbH	Cloud Infrastructure & Hosting	Germany / Finland (EEA)
Soverin	Email	The Netherlands (EEA)
Uptime Robot	Status page (if accessed by user)	Slovak Republic (EEA)

Mon, 01 Jan 0001 00:00:00 +0000

Terms of Service — OpenCommit#

Effective Date: 2026-01-31
Last Updated: 2026-04-04

These Terms of Service (“Terms”) constitute a legally binding agreement between the OpenCommit Foundation (Stichting OpenGit, a foundation (stichting)) established under the laws of The Netherlands, with its statutory seat in Leiden, the Netherlands (“OpenCommit”, “we”, “us”, “our”), and you (“User”, “you”).

These Terms govern your access to and use of the OpenCommit platform available at https://opencommit.eu and related services (the “Service”).