f2cdb2fa66
- Upstream chosen `Handlebars` as language for the templates, presumenly because Github doesn't have an syntax highlighter for Go. - Forgejo does have syntax highlighting support for Go templates, so use that. (cherry picked from commit a79718522dc432e32cf322498ddf22ec570fa8fd) (cherry picked from commit 380d847e5cdb179292c7bd1a5e3e6839fb8b31dd) (cherry picked from commit 4126a9672d93fc33b72fb816a404056aac64dfc8) (cherry picked from commit afde0ed82271df540348953a811a8e9db1a83343) (cherry picked from commit 6ddaca00615340958e1aecca2c4807e39a2b1eff) (cherry picked from commit 454b2f6b35c018cc631dd8847ae9d3243d9adc37) (cherry picked from commit 58c10e1f93da8d8f193936eff00ebd86ecd8b78c) (cherry picked from commit 19ec0a5536204105be78744b436a35710d8e8702) (cherry picked from commit c3717ae4deb8acb43f861675dc44f689def544ed) (cherry picked from commit 6c74bbe5757b290c2fe5ea13cd980a2b11fb207e) (cherry picked from commit 9cb48db780c3592a6aa1df2770a309729eca35f6) (cherry picked from commit 19cb774553302a7ece9d653d052b6de4c47de687) (cherry picked from commit ac35eb83cd6f34da6079ec4ba8d00390aa56a0c0) (cherry picked from commit 986a306d221b14891d1e5776ad3088d5636595cb) (cherry picked from commit |
||
---|---|---|
.devcontainer | ||
.forgejo | ||
.gitea | ||
assets | ||
build | ||
cmd | ||
contrib | ||
custom/conf | ||
docker | ||
docs | ||
models | ||
modules | ||
options | ||
public | ||
releases/images | ||
routers | ||
services | ||
snap | ||
templates | ||
tests | ||
web_src | ||
.air.toml | ||
.changelog.yml | ||
.dockerignore | ||
.editorconfig | ||
.eslintrc.yaml | ||
.gitattributes | ||
.gitignore | ||
.gitpod.yml | ||
.golangci.yml | ||
.ignore | ||
.markdownlint.yaml | ||
.npmrc | ||
.spectral.yaml | ||
.stylelintrc.yaml | ||
.yamllint.yaml | ||
BSDmakefile | ||
build.go | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
DCO | ||
Dockerfile | ||
Dockerfile.rootless | ||
go.mod | ||
go.sum | ||
LICENSE | ||
main.go | ||
MAINTAINERS | ||
Makefile | ||
package-lock.json | ||
package.json | ||
playwright.config.js | ||
poetry.lock | ||
poetry.toml | ||
pyproject.toml | ||
README.md | ||
RELEASE-NOTES.md | ||
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.