Beyond coding. We forge. https://forgejo.org
Find a file
yp05327 49eb831663
Fix Null Pointer error for CommitStatusesHideActionsURL (#31731)
Fix https://github.com/go-gitea/gitea/pull/30156#discussion_r1695247028

Forgot fixing it in #31719

(cherry picked from commit 0a11bce87f07233d5f02554b8f3b4a2aabd37769)
2024-08-04 10:14:34 +02:00
.devcontainer
.forgejo chore(ci): do not hardcode go version, use go.mod instead 2024-08-03 11:53:55 +02:00
assets
build
cmd
contrib
custom/conf Add signature support for the RPM module (#4780) 2024-08-02 05:56:57 +00:00
docker
models Fix Null Pointer error for CommitStatusesHideActionsURL (#31731) 2024-08-04 10:14:34 +02:00
modules Arch packages implementation (#4785) 2024-08-04 06:16:29 +00:00
options Arch packages implementation (#4785) 2024-08-04 06:16:29 +00:00
public Arch packages implementation (#4785) 2024-08-04 06:16:29 +00:00
release-notes feat(quota): Add a terse release not about quotas 2024-08-02 11:10:34 +02:00
releases/images
routers Set owner id to zero when GetRegistrationToken for repo (#31725) 2024-08-04 10:14:34 +02:00
services Move registerActionsCleanup to initActionsTasks (#31721) 2024-08-04 10:14:34 +02:00
templates Fix API endpoint for registration-token (#31722) 2024-08-04 10:14:34 +02:00
tests Arch packages implementation (#4785) 2024-08-04 06:16:29 +00:00
tools
web_src Arch packages implementation (#4785) 2024-08-04 06:16:29 +00:00
.air.toml
.deadcode-out
.dockerignore
.editorconfig
.envrc
.eslintrc.yaml
.gitattributes
.gitignore
.gitmodules
.gitpod.yml
.golangci.yml
.ignore
.markdownlint.yaml
.npmrc
.release-notes-assistant.yaml
.spectral.yaml
.yamllint.yaml
BSDmakefile
build.go
CODEOWNERS
CONTRIBUTING.md
DCO
Dockerfile
Dockerfile.rootless
flake.lock
flake.nix
go.mod chore(ci): do not hardcode go version, use go.mod instead 2024-08-03 11:53:55 +02:00
go.sum Add signature support for the RPM module (#4780) 2024-08-02 05:56:57 +00:00
LICENSE
main.go
Makefile
package-lock.json
package.json
playwright.config.js
poetry.lock
poetry.toml
pyproject.toml
README.md
release-notes-assistant.sh
RELEASE-NOTES.md
renovate.json
stylelint.config.js
tailwind.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.