meowmeow
Find a file
Gusted 5a93b267b0
[BRANDING] security.txt
- The [security.txt](https://securitytxt.org/) is a standardized file to
help with reporting security vulnerabilities, by having the most essential
information served at `.well-known/security.txt`.
- Brand this file to point to the Forgejo security team.
- Resolves https://codeberg.org/forgejo/forgejo/issues/1192

(cherry picked from commit 7ca1d0ec87bc23881f59ce3ea04390bf508ec0fa)
(cherry picked from commit ba974b016199cd279b8c7aca76a936910e9f4d69)
(cherry picked from commit 966fbcdcfdc8027aa31fe46eafa229854fe120ad)
(cherry picked from commit 8b9efebc6e5a211b64b003284bf3bb8c66c85662)
(cherry picked from commit 91b1c84c1873b6e07ff7e700429a4fc6f6c1e3bf)
(cherry picked from commit 30ade1ea0b6de3b634283bd3741b49abf37f9bf0)
(cherry picked from commit 15ec35014e1afda4010e1956722ab9ba78d53093)
(cherry picked from commit a5e8bb4a93ede29c077d246c984d4aa0da70a4ec)
(cherry picked from commit 273b03888f4e71009474a384c38cef605d2763a2)
(cherry picked from commit 69b6b53fe5d94ab34d3f47d2327e1915fa883cde)
(cherry picked from commit b00a74917ce3167344140786be49c185a5b8cd79)
(cherry picked from commit 3ea219777b0bdfba6b1063c5eb20c4546710a208)
(cherry picked from commit 4be13aa6265e7f552ac6a4df9e5763b944b6fb1a)
(cherry picked from commit 03ddd40ab9cc28ae759f08d2af09171cb5b4aed6)
2023-11-06 15:47:25 +01:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [UPGRADE] add sanity check for v1.20.5-0 2023-11-06 14:56:37 +01:00
.gitea [WORKFLOW] yaml issue templates 2023-11-06 14:56:37 +01:00
.github delete Gitea specific files that need rewriting for Forgejo 2023-11-06 14:54:04 +01:00
assets [BRANDING] add Forgejo logo 2023-11-06 15:47:24 +01:00
build Use Set[Type] instead of map[Type]bool/struct{}. (#26804) 2023-08-30 06:55:25 +00:00
cmd [BRANDING] Rebrand dump log 2023-11-06 15:47:25 +01:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-11-06 15:47:25 +01:00
custom/conf [BRANDING] Rebrand default config settings for new installs (#140) 2023-11-06 15:47:24 +01:00
docker [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-11-06 15:47:24 +01:00
docs refactor postgres connection string building (#27723) (#27869) 2023-11-01 23:19:02 +00:00
models [BRANDING] Use forgejo binary name 2023-11-06 15:47:25 +01:00
modules [BRANDING] parse FORGEJO__* in the container environment 2023-11-06 15:47:25 +01:00
options [BRANDING] Replace links to GitHub with Codeberg guides about adding SSH/GPG keys 2023-11-06 15:47:25 +01:00
public [BRANDING] security.txt 2023-11-06 15:47:25 +01:00
releases/images [DOCS] RELEASE-NOTES.md 2023-11-06 14:54:05 +01:00
routers [BRANDING] Use forgejo binary name 2023-11-06 15:47:25 +01:00
services [BRANDING] add the forgejo webhook type & update webhook docs URLs 2023-11-06 15:47:25 +01:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates [BRANDING] Replace links to GitHub with Codeberg guides about adding SSH/GPG keys 2023-11-06 15:47:25 +01:00
tests [BRANDING] Update nodeinfo branding 2023-11-06 15:47:25 +01:00
web_src [BRANDING] Add Forgejo light, dark, and auto themes 2023-11-06 15:47:24 +01:00
.air.toml Reduce verbosity of dev commands (#24917) 2023-05-24 20:11:04 +00:00
.changelog.yml Adapt .changelog.yml to new labeling system (#27701) (#27702) 2023-10-20 00:29:50 +02:00
.dockerignore Move public asset files to the proper directory (#25907) 2023-07-18 18:06:43 +02:00
.editorconfig Add markdownlint (#20512) 2022-07-28 09:22:47 +08:00
.eslintrc.yaml Update JS and PY dependencies (#27501) (#27518) 2023-10-08 19:31:33 +02:00
.gitattributes [META] Use correct language for .tmpl 2023-11-06 14:56:37 +01:00
.gitignore [CI] gitignore: emacs backups 2023-11-06 14:12:41 +01:00
.gitpod.yml Add Github related extensions in devcontainer (#25800) 2023-07-14 15:58:02 +08:00
.golangci.yml Use Go 1.21 for golangci-lint (#26786) 2023-08-29 16:25:24 +02:00
.ignore Add /public/assets to .ignore (#26232) 2023-07-30 12:34:20 +02:00
.markdownlint.yaml Enable markdownlint no-duplicate-header (#27500) (#27506) 2023-10-07 21:41:41 +08:00
.npmrc Upgrade to npm lockfile v3 and explicitely set it (#23561) 2023-03-18 19:38:10 +01:00
.spectral.yaml Add spectral linter for Swagger (#20321) 2022-07-11 18:07:16 -05:00
.stylelintrc.yaml Update JS dependencies (#26025) 2023-07-21 11:34:10 +08:00
.yamllint.yaml fully replace drone with actions (#27556) (#27575) 2023-10-11 12:03:06 +00:00
BSDmakefile Fix build errors on BSD (in BSDMakefile) (#27594) (#27608) 2023-10-14 07:29:55 +00:00
build.go User/Org Feed render description as per web (#23887) 2023-04-04 04:39:47 +01:00
CHANGELOG.md Add 1.20.5 changelog (#27404) (#27412) 2023-10-03 22:21:19 +08:00
CODEOWNERS [META] Add CODEOWNERS files 2023-11-06 14:56:38 +01:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-11-06 14:54:05 +01:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [CI] Forgejo Actions based release process (squash) gitea to forgejo 2023-11-06 15:47:25 +01:00
Dockerfile.rootless [CI] Forgejo Actions based release process (squash) gitea to forgejo 2023-11-06 15:47:25 +01:00
go.mod Upgrade xorm to 1.3.4 (#27807) (#27813) 2023-10-27 14:17:27 +02:00
go.sum Upgrade xorm to 1.3.4 (#27807) (#27813) 2023-10-27 14:17:27 +02:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-11-06 14:54:05 +01:00
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-11-06 15:47:25 +01:00
MAINTAINERS Apply lng2020 to maintainers (#27068) 2023-09-14 12:10:12 +08:00
Makefile [BRANDING] add forgejo target to Makefile 2023-11-06 15:47:25 +01:00
package-lock.json Update JS and PY dependencies (#27501) (#27518) 2023-10-08 19:31:33 +02:00
package.json Update JS and PY dependencies (#27501) (#27518) 2023-10-08 19:31:33 +02:00
playwright.config.js Update JS dependencies and eslint config (#21388) 2022-10-10 20:02:20 +08:00
poetry.lock Update JS and PY dependencies (#27501) (#27518) 2023-10-08 19:31:33 +02:00
poetry.toml Clean up pyproject.toml and package.json, fix poetry options (#25327) 2023-06-18 18:13:08 +00:00
pyproject.toml [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-11-06 15:47:24 +01:00
README.md [BRANDING] add Forgejo logo 2023-11-06 15:47:24 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-11-06 14:54:05 +01:00
vitest.config.js Use vitest globals (#27102) (#27311) 2023-09-27 16:10:08 +02:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2023-11-06 14:56:35 +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.