No description
Find a file
Gusted 8d36b5cce6
[GITEA] Make atomic ssh keys replacement robust
- After stumbling upon https://github.com/golang/go/issues/22397 and
reading the implementations I realized that Forgejo code doesn't have
`Sync()` and it doesn't properly error handle the `Close` function.
- (likely) Resolves https://codeberg.org/forgejo/forgejo/issues/1446

(cherry picked from commit 0efcb334c2)
(cherry picked from commit 04ef02c0dd)
(cherry picked from commit 85f2065c9b)
2023-10-16 17:00:07 +02:00
.devcontainer
.forgejo
.gitea [WORKFLOW] yaml issue templates 2023-10-16 14:37:58 +02:00
.github
assets
build
cmd
contrib
custom/conf [GITEA] notifies admins on new user registration 2023-10-16 16:54:52 +02:00
docker
docs [GITEA] notifies admins on new user registration 2023-10-16 16:54:52 +02:00
models [GITEA] Make atomic ssh keys replacement robust 2023-10-16 17:00:07 +02:00
modules [GITEA] Remove SSH workaround 2023-10-16 17:00:07 +02:00
options [GITEA] Detect file rename and show in history 2023-10-16 16:55:04 +02:00
public [FEAT] add Forgero Git Service 2023-10-16 14:37:58 +02:00
releases/images
routers [v1.22] [GITEA] Drop sha256-simd in favor of stdlib 2023-10-16 16:59:49 +02:00
services [v1.22] [GITEA] Drop sha256-simd in favor of stdlib 2023-10-16 16:59:49 +02:00
snap
templates [GITEA] fix indentation in Maven package install instructions 2023-10-16 16:55:04 +02:00
tests [v1.22] [GITEA] Drop sha256-simd in favor of stdlib 2023-10-16 16:59:49 +02:00
web_src [GITEA] Use vertical tabs on issue filters 2023-10-16 16:53:49 +02:00
.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
CODEOWNERS [META] Add CODEOWNERS files 2023-10-16 14:37:59 +02:00
CONTRIBUTING.md
DCO
Dockerfile
Dockerfile.rootless
go.mod [GITEA] Remove SSH workaround 2023-10-16 17:00:07 +02:00
go.sum [GITEA] Remove SSH workaround 2023-10-16 17:00:07 +02: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.