Go to file
Gusted 4d0a1e0637
[GITEA] Fix NPE in UsernameSubRoute
- When the user is not found in `reloadparam`, early return when the
user is not found to avoid calling `IsUserVisibleToViewer` which in turn
avoids causing a NPE.
- This fixes the case that a 500 error and 404 error is shown on the
same page.
- Add integration test for non-existant user RSS.
- Regression by c6366089df

(cherry picked from commit f0e0696278)
(cherry picked from commit 75d8066908)
2024-01-01 15:36:17 +01:00
.devcontainer
.forgejo
.gitea
assets [GITEA] Use maintained gziphandler 2024-01-01 15:23:53 +01:00
build
cmd
contrib [GITEA] fix VSCode settings 2024-01-01 15:27:12 +01:00
custom/conf [GITEA] Revert "Deprecate query string auth tokens (#28390)" 2024-01-01 15:36:17 +01:00
docker
docs [GITEA] notifies admins on new user registration 2024-01-01 15:20:56 +01:00
models [GITEA] Allow changing the email address before activation 2024-01-01 15:36:14 +01:00
modules [GITEA] Revert "Deprecate query string auth tokens (#28390)" 2024-01-01 15:36:17 +01:00
options [GITEA] Allow changing the email address before activation 2024-01-01 15:36:14 +01:00
public
releases/images
routers [GITEA] Fix NPE in UsernameSubRoute 2024-01-01 15:36:17 +01:00
services [GITEA] the ref of a scheduled action is always the default branch 2024-01-01 15:36:17 +01:00
snap
templates [GITEA] Revert "Deprecate query string auth tokens (#28390)" 2024-01-01 15:36:17 +01:00
tests [GITEA] Fix NPE in UsernameSubRoute 2024-01-01 15:36:17 +01:00
web_src [GITEA] Use vertical tabs on issue filters 2024-01-01 15:20:56 +01:00
.air.toml
.changelog.yml
.deadcode-out [GITEA] Enable mocked HTTP responses for GitLab migration test 2024-01-01 15:24:08 +01:00
.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
CODEOWNERS
CONTRIBUTING.md
DCO
Dockerfile
Dockerfile.rootless
go.mod [GITEA] Use existing error functionality 2024-01-01 15:24:07 +01:00
go.sum [GITEA] Use maintained gziphandler 2024-01-01 15:23:53 +01:00
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.