No description
Find a file
Loïc Dachary 1d268662cc
[BRANDING] lookup .forgejo/workflows before .gitea/workflows
(cherry picked from commit ffe51fd72f)
(cherry picked from commit a2b483b67d)
(cherry picked from commit 2b7d0bbde2)
(cherry picked from commit 3027fddbff)
(cherry picked from commit 023f7cc3b2)
(cherry picked from commit 95c3a3aa70)
(cherry picked from commit 1cc0ef5cc5)
(cherry picked from commit 467d082568)
(cherry picked from commit 5d8f40e865)
2023-05-02 13:36:45 +02:00
.gitea [WORKFLOW] issues & pr templates 2023-05-02 10:56:29 +02:00
.github/workflows delete Gitea specific files that need rewriting for Forgejo 2023-05-02 10:56:26 +02:00
.woodpecker [BRANDING] parse FORGEJO__* in the container environment 2023-05-02 13:36:40 +02:00
assets [BRANDING] add Forgejo logo 2023-05-02 13:22:45 +02:00
build Ensure final newline in assets/go-licenses.json (#24407) 2023-04-28 13:39:18 -04:00
cmd [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-05-02 13:36:40 +02:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-05-02 13:36:40 +02:00
CONTRIBUTING [DOCS] CONTRIBUTING 2023-05-02 10:56:29 +02:00
custom/conf [BRANDING] DEFAULT_ACTIONS_URL = https://codeberg.org 2023-05-02 13:36:44 +02:00
docker [BRANDING] container images: set APP_NAME 2023-05-02 13:26:33 +02:00
docs [BRANDING] DEFAULT_ACTIONS_URL = https://codeberg.org 2023-05-02 13:36:44 +02:00
models [BRANDING] reserve forgejo-actions username 2023-05-02 13:36:44 +02:00
modules [BRANDING] lookup .forgejo/workflows before .gitea/workflows 2023-05-02 13:36:45 +02:00
options [skip ci] Updated translations via Crowdin 2023-05-02 00:23:19 +00:00
public [BRANDING] Custom loading animation for Forgejo 2023-05-02 13:26:33 +02:00
releases [DOCS] RELEASE-NOTES.md 2023-05-02 10:56:29 +02:00
routers [BRANDING] Update nodeinfo branding 2023-05-02 13:36:44 +02:00
services [BRANDING] define the forgejo webhook type 2023-05-02 13:36:40 +02:00
snap
templates [BRANDING] define the forgejo webhook type 2023-05-02 13:36:40 +02:00
tests [BRANDING] Update nodeinfo branding 2023-05-02 13:36:44 +02:00
web_src [BRANDING] Add Forgejo light, dark, and auto themes 2023-05-02 13:36:36 +02:00
.air.toml Set stop_on_error (#24453) 2023-04-30 18:31:16 -04:00
.changelog.yml
.dockerignore
.drone.yml replace PR docker dry run in drone with Actions (#24475) 2023-05-01 16:39:36 -04:00
.editorconfig
.eslintrc.yaml Add eslint-plugin-regexp (#24361) 2023-04-26 22:08:16 -04:00
.gitattributes Mark /templates/swagger/v1_json.tmpl as generated file (#24306) 2023-04-24 13:18:24 -04:00
.gitignore [CI] implementation: Woodpecker based CI 2023-05-02 10:14:28 +02:00
.gitpod.yml Remove docs from automatically building in Gitpod (#23978) 2023-04-07 15:55:25 -04:00
.golangci.yml Enable forbidigo linter (#24278) 2023-04-24 05:50:58 -04:00
.ignore
.markdownlint.yaml
.npmrc Upgrade to npm lockfile v3 and explicitely set it (#23561) 2023-03-18 19:38:10 +01:00
.spectral.yaml
.stylelintrc.yaml Update JS deps (#23853) 2023-04-02 19:47:14 -04:00
BSDmakefile update BSDmakefile to latest version from upstream (#24063) 2023-04-11 23:42:22 -04:00
build.go User/Org Feed render description as per web (#23887) 2023-04-04 04:39:47 +01:00
CHANGELOG.md Changelog 1.19.2 (#24365) (#24403) 2023-04-28 15:20:52 -04:00
CODE_OF_CONDUCT.md Add Gitea Community Code of Conduct (#23188) 2023-03-09 10:49:34 +08:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-05-02 10:56:29 +02:00
DCO
Dockerfile [CI] implementation: forgejo container images 2023-05-02 10:14:30 +02:00
Dockerfile.rootless [CI] implementation: forgejo container images 2023-05-02 10:14:30 +02:00
go.mod Revert "Add Debian package registry" (#24412) 2023-04-28 18:06:41 -04:00
go.sum Revert "Add Debian package registry" (#24412) 2023-04-28 18:06:41 -04:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-05-02 10:56:29 +02:00
main.go add CLI command to register runner tokens (#23762) 2023-04-17 13:07:13 -04:00
MAINTAINERS Apply to become maintainer (#24254) 2023-04-21 21:23:16 +08:00
Makefile [BRANDING] Replace branding in Swagger 2023-05-02 13:36:40 +02:00
package-lock.json Remove font-awesome and fomantic icon module (#24471) 2023-05-01 13:25:54 -04:00
package.json Remove font-awesome and fomantic icon module (#24471) 2023-05-01 13:25:54 -04:00
playwright.config.js
README.md [BRANDING] add Forgejo logo 2023-05-02 13:22:45 +02:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES: 1.19.2-0 2023-05-02 11:02:55 +02:00
vitest.config.js Update JS dependencies (#24218) 2023-04-19 22:36:41 -04:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2023-05-02 11:02:53 +02:00

Welcome to Forgejo

Hi there! Tired of big platforms playing monopoly? Providing Git hosting for your project, friends, company or community? Forgejo (/for'd͡ʒe.jo/ inspired by forĝejo the Esperanto word for forge) has you covered with its intuitive interface, light and easy hosting and a lot of builtin functionality.

Forgejo was created in 2022 because we think that the project should be owned by an independent community. If you second that, then Forgejo is for you! Our promise: Independent Free/Libre Software forever!

What does Forgejo offer?

If you like any of the following, Forgejo is literally meant for you:

  • Lightweight: Forgejo can easily be hosted on nearly every machine. Running on a Raspberry? Small cloud instance? No problem!
  • Project management: Besides Git hosting, Forgejo offers issues, pull requests, wikis, kanban boards and much more to coordinate with your team.
  • Publishing: Have something to share? Use releases to host your software for download, or use the package registry to publish it for docker, npm and many other package managers.
  • Customizable: Want to change your look? Change some settings? There are many config switches to make Forgejo work exactly like you want.
  • Powerful: Organizations & team permissions, CI integration, Code Search, LDAP, OAuth and much more. If you have advanced needs, Forgejo has you covered.
  • Privacy: From update checker to default settings: Forgejo is built to be privacy first for you and your crew.
  • Federation: (WIP) We are actively working to connect software forges with each other through ActivityPub, and create a collaborative network of personal instances.

Learn more

Dive into the documentation, subscribe to releases and blog post on our website, find us on the Fediverse or hop into our Matrix room if you have any questions or want to get involved.

Get involved

If you are interested in making Forgejo better, either by reporting a bug or by changing the governance, please take a look at the contribution guide.