No description
Find a file
Gergely Nagy 1868dec2e4
[GITEA] repo: Don't redirect the repo to external units
When displaying the repo home view, do not redirect to unit types that
can't be defaults (which, at the moment, are the external wiki and issue
tracker unit types).

If we'd redirect to those, that would mean that a repository with the
Code unit disabled, and an external issue tracker would immediately
redirect to the external issue tracker, making it harder to reach other,
non-external units of the repo.

Fixes #1965.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
(cherry picked from commit 44078e5460)
2024-01-08 17:11:56 +01:00
.devcontainer
.forgejo [CI] push forgejo branches to the specified destination 2024-01-08 13:37:01 +01:00
.gitea [WORKFLOW] yaml issue templates 2024-01-08 14:01:18 +01:00
assets [GITEA] Use maintained gziphandler 2024-01-08 16:59:19 +01:00
build
cmd [CLI] implement forgejo-cli 2024-01-08 13:37:00 +01:00
contrib [GITEA] fix VSCode settings 2024-01-08 17:05:47 +01:00
custom/conf [GITEA] Revert "Deprecate query string auth tokens (#28390)" 2024-01-08 17:05:47 +01:00
docker Dockerfile small refactor (#27757) 2023-10-29 09:44:06 +08:00
docs [GITEA] notifies admins on new user registration 2024-01-08 16:55:44 +01:00
models [GITEA] Fix session generation for database (squash) timeutil.Mock 2024-01-08 17:05:48 +01:00
modules [GITEA] Configurable clone methods 2024-01-08 17:05:48 +01:00
options [GITEA] Configurable clone methods 2024-01-08 17:05:48 +01:00
public [API] Forgejo API /api/forgejo/v1 2024-01-08 14:01:17 +01:00
releases/images [DOCS] RELEASE-NOTES.md 2024-01-08 14:01:17 +01:00
routers [GITEA] repo: Don't redirect the repo to external units 2024-01-08 17:11:56 +01:00
services [GITEA] notifies admins on new user registration (squash) DeleteByID 2024-01-08 17:05:48 +01:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates [GITEA] Configurable clone methods 2024-01-08 17:05:48 +01:00
tests [GITEA] repo: Don't redirect the repo to external units 2024-01-08 17:11:56 +01:00
web_src [GITEA] Use vertical tabs on issue filters 2024-01-08 16:52:44 +01:00
.air.toml
.changelog.yml Adapt .changelog.yml to new labeling system (#27701) 2023-10-20 00:22:00 +02:00
.deadcode-out [GITEA] Enable mocked HTTP responses for GitLab migration test 2024-01-08 17:05:46 +01:00
.dockerignore
.editorconfig
.eslintrc.yaml Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01:00
.gitattributes [META] Use correct language for .tmpl 2024-01-08 14:01:18 +01:00
.gitignore [DEVELOPMENT] added /local/ to .gitignore 2024-01-08 14:01:19 +01:00
.gitpod.yml
.golangci.yml Remove go versions from .golangci.yml (#27953) 2023-11-07 22:03:27 +01:00
.ignore
.markdownlint.yaml Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
.npmrc
.spectral.yaml
.stylelintrc.yaml Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
.yamllint.yaml fully replace drone with actions (#27556) 2023-10-11 06:39:32 +00:00
BSDmakefile Fix build errors on BSD (in BSDMakefile) (#27594) 2023-10-13 15:38:27 +00:00
build.go
CHANGELOG.md Fix release link in changelog for v1.21.0 2023-11-14 15:03:49 +01:00
CODEOWNERS [META] Add CODEOWNERS files 2024-01-08 14:01:18 +01:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2024-01-08 14:01:17 +01:00
DCO
Dockerfile [CI] Forgejo Actions based release process 2024-01-08 13:37:01 +01:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2024-01-08 13:37:01 +01:00
go.mod [GITEA] Use existing error functionality 2024-01-08 16:59:19 +01:00
go.sum [GITEA] Use maintained gziphandler 2024-01-08 16:59:19 +01:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2024-01-08 14:01:17 +01:00
main.go [SEMVER] store SemVer in ForgejoSemVer after a database upgrade 2024-01-08 14:01:18 +01:00
MAINTAINERS Apply to become a maintainer (#27522) 2023-10-08 10:36:40 -04:00
Makefile [SEMVER] 7.0.0+0-gitea-1.22.0 2024-01-08 14:02:28 +01:00
package-lock.json Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
package.json Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
playwright.config.js
poetry.lock Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01:00
poetry.toml
pyproject.toml Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01:00
README.md [DOCS] README 2024-01-08 14:01:17 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2024-01-08 14:01:17 +01:00
vitest.config.js Use vitest globals (#27102) 2023-09-27 04:37:13 +00:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2024-01-08 14:01:17 +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.