Forgejo Contributor Guide

This area is targeted to people who want to improve Forgejo and adjust it to
their needs.
We encourage you to read our warm welcome first, then get involved.
For everyone involved
Code of Conduct
Bugs, enhancement ideas and development roadmap
General discussions related to Forgejo (tips & tricks, news, ideas, questions)
Governance
Sustainability and funding repository
Translations
Localization - for translators
English strings - for developers or people improving strings
Weblate admin duties - for Forgejo contributors
For UI/UX designers and user researchers
Design repository
User Research repository
For developers
Compiling from source
Testing
Development environment
Finding what to work on
Interface customization
Web browser support
Architecture overview
Federation Architecture
Federation Architectural Decision Records
Repository Migration
Service Messages
Threat Analysis
Developer Certificate of Origin (DCO)
code.forgejo.org
next.forgejo.org kubernetes infrastructure
static pages
Forgejo Runner implementation notes
Dependency management
For maintainers
Hardware infrastructure
Release management
Managing dependencies between repositories
Secrets
When you've contributed something, you'll have learned new things in the process.
Why not share those things with other contributors?
Creating a personal article is an option to do so.
Once you do, create a Pull Request on this page and extend the list.
Forgejo Action Notification Development (including exhaustive development and testing setup) by Christopher Besch on 20th November 2025
The History of Forgejo's Pub-Sub Pattern by Christopher Besch on 30th October 2025