Beyond coding. We forge.
Find a file
silverwind 22c694a9e9
[gitea] add lint-spell-fix to lint-fix (#29111)
Followup to https://github.com/go-gitea/gitea/pull/29106, fix this
oversight.

(cherry picked from commit c7a21cbb0c5f8302495fa24baf218dc3462de2c5)
2024-02-10 10:53:43 +01:00
.devcontainer
.forgejo [CI] cascade end-to-end must not try to merge feature branches 2024-02-10 10:53:04 +01:00
.gitea
assets
build
cmd [gitea] Fix push to create with capitalize repo name (#29090) 2024-02-10 10:53:43 +01:00
contrib
custom/conf
docker
docs [gitea] Rework spellchecking, add lint-spell (#29106) 2024-02-10 10:53:43 +01:00
manual-testing@877d11b403 [TESTS] add manual testing instructions as a sub-module 2024-02-08 11:43:43 +01:00
models [gitea] Remove unnecessary parameter (#29092) 2024-02-10 10:53:43 +01:00
modules [gitea] Refactor parseSignatureFromCommitLine (#29054) 2024-02-10 10:53:43 +01:00
options [gitea] [skip ci] Updated translations via Crowdin 2024-02-10 10:53:42 +01:00
public
releases/images
routers [gitea] Display friendly error message (#29105) 2024-02-10 10:53:43 +01:00
services [gitea] Fix missing link on outgoing new release notifications (#29079) 2024-02-10 10:53:43 +01:00
snap
templates [gitea] Rework spellchecking, add lint-spell (#29106) 2024-02-10 10:53:43 +01:00
tests Merge remote-tracking branch 'forgejo/forgejo-dependency' into wip-forgejo 2024-02-09 19:00:54 +01:00
web_src [gitea] Move vitest setup file to root (#29097) 2024-02-10 10:53:43 +01:00
.air.toml
.changelog.yml
.deadcode-out
.dockerignore
.editorconfig
.eslintrc.yaml [gitea] Fix gitea-origin-url with default ports (#29085) 2024-02-10 10:53:43 +01:00
.gitattributes
.gitignore
.gitmodules [TESTS] add manual testing instructions as a sub-module 2024-02-08 11:43:43 +01:00
.gitpod.yml
.golangci.yml
.ignore
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
.yamllint.yaml
BSDmakefile
build.go
CHANGELOG.md
CODEOWNERS
CONTRIBUTING.md
DCO
Dockerfile
Dockerfile.rootless
go.mod
go.sum
LICENSE
main.go
MAINTAINERS
Makefile [gitea] add lint-spell-fix to lint-fix (#29111) 2024-02-10 10:53:43 +01:00
package-lock.json [gitea] Remove lightningcss (#29070) 2024-02-10 10:53:43 +01:00
package.json [gitea] Use defaults browserslist (#29098) 2024-02-10 10:53:43 +01:00
playwright.config.js
poetry.lock
poetry.toml
pyproject.toml
README.md
RELEASE-NOTES.md
vitest.config.js [gitea] Move vitest setup file to root (#29097) 2024-02-10 10:53:43 +01:00
webpack.config.js [gitea] Remove lightningcss (#29070) 2024-02-10 10:53:43 +01: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.