My Forgejo fork. Changes are in FORK.md.
Go to file
2024-04-03 19:00:16 +00:00
.devcontainer
.forgejo [CI] backport auto-squash detection and -x 2024-04-03 08:18:39 +02:00
.gitea pull_request_template: test/needed label 2024-03-22 10:11:47 +01:00
assets
build
cmd Merge pull request '[FEAT] Allow non-explicit push options' (#2984) from gusted/forgejo-push-options into forgejo 2024-04-03 19:00:16 +00:00
contrib
custom/conf
docker [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2024-02-05 16:02:14 +01:00
docs
manual-testing@877d11b403
models
modules
options
public Customizable "Open with" applications for repository clone (#29320) 2024-03-23 11:58:54 +01:00
releases/images
routers
services Merge pull request '[FEAT] Configure if protected branch rule should apply to admins' (#2867) from gusted/forgejo-protectedbranch-admins into forgejo 2024-04-01 19:28:29 +00:00
templates
tests
tools Add svg linter and fix incorrect svgs (#30086) 2024-03-30 07:17:30 +01:00
web_src
.air.toml Exclude routers/private/tests from air (#29949) 2024-03-26 19:04:26 +01:00
.changelog.yml
.deadcode-out
.dockerignore
.editorconfig
.eslintrc.yaml
.gitattributes
.gitignore move some scripts from 'build' to 'tools' directory, misc refactors (#29844) 2024-03-26 19:04:25 +01:00
.gitmodules
.gitpod.yml
.golangci.yml
.ignore
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
.yamllint.yaml fully replace drone with actions (#27556) 2023-10-11 06:39:32 +00:00
BSDmakefile
build.go User/Org Feed render description as per web (#23887) 2023-04-04 04:39:47 +01:00
CHANGELOG.md Fix release link in changelog for v1.21.0 2023-11-14 15:03:49 +01:00
CODEOWNERS
CONTRIBUTING.md
DCO
Dockerfile go: upgrade to go v1.22 - Dockerfile* 2024-03-26 06:48:32 +01:00
Dockerfile.rootless go: upgrade to go v1.22 - Dockerfile* 2024-03-26 06:48:32 +01:00
go.mod Merge pull request 'Update module github.com/editorconfig/editorconfig-core-go/v2 to v2.6.2' (#2987) from renovate/github.com-editorconfig-editorconfig-core-go-v2-2.x into forgejo 2024-04-03 16:56:21 +00:00
go.sum
LICENSE
main.go
MAINTAINERS
Makefile
package-lock.json
package.json
playwright.config.js
poetry.lock Update JS any PY dependencies, remove workarounds (#30085) 2024-03-30 07:17:30 +01:00
poetry.toml
pyproject.toml
README.md [BRANDING] add Forgejo logo 2024-02-05 16:02:13 +01:00
RELEASE-NOTES.md
renovate.json
tailwind.config.js
updates.config.js
vitest.config.js
webpack.config.js

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.