fedi/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-11-22 13:45:19 +00:00
Code Issues Packages Projects Releases Wiki Activity
Beyond coding. We forge. (Code of Conduct: https://codeberg.org/forgejo/code-of-conduct)
16696 commits 10 branches 235 tags 595 MiB
Go 73.9%
go-html-template 11.3%
JavaScript 5%
Roff 4.7%
CSS 3.2%
Other 1.7%
Go to file
Loïc Dachary 079e0efb01
[BRANDING] add forgejo target to Makefile 
The gitea target is kept as is, for the sake of compatibility with
build systems that rely on it. The forgejo target creates a hard link
with forgejo.

(cherry picked from commit ce156c7cb4)
(cherry picked from commit b2cb232825)
(cherry picked from commit 85543c22bd)
(cherry picked from commit 302955a20d)
(cherry picked from commit 4b1be0858e)
(cherry picked from commit afed1a6e20)
(cherry picked from commit e81304bcd1)
(cherry picked from commit 479cd51a03)
(cherry picked from commit 8baab7c0c1)
(cherry picked from commit 5d25ad9f09)
(cherry picked from commit f36942789f)
(cherry picked from commit 9abfbae8a0)
2023-10-09 20:59:39 +02:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [CI] Forgejo Actions based release process (squash) use forgejo-curl.sh 2023-10-09 19:30:21 +02:00
.gitea [WORKFLOW] yaml issue templates 2023-10-09 19:11:03 +02:00
.github delete Gitea specific files that need rewriting for Forgejo 2023-10-09 18:46:36 +02:00
assets [BRANDING] add Forgejo logo 2023-10-09 20:51:47 +02: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-10-09 20:59:39 +02:00
contrib [BRANDING] parse FORGEJO__* in the container environment 2023-10-09 20:59:39 +02:00
custom/conf [BRANDING] Rebrand default config settings for new installs (#140) 2023-10-09 20:51:47 +02:00
docker [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-10-09 20:59:38 +02:00
docs Add docs section for sub-paths with the container registry (#27505) 2023-10-09 12:45:41 +08:00
models [BRANDING] Use forgejo binary name 2023-10-09 20:59:39 +02:00
modules [BRANDING] parse FORGEJO__* in the container environment 2023-10-09 20:59:39 +02:00
options [FEAT] add Forgero Git Service 2023-10-09 19:11:03 +02:00
public [BRANDING] Custom loading animation for Forgejo 2023-10-09 20:51:47 +02:00
releases/images [DOCS] RELEASE-NOTES.md 2023-10-09 19:11:01 +02:00
routers [BRANDING] Use forgejo binary name 2023-10-09 20:59:39 +02:00
services [BRANDING] add the forgejo webhook type & update webhook docs URLs 2023-10-09 20:59:39 +02:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2023-10-09 20:59:39 +02:00
tests [BRANDING] Update nodeinfo branding 2023-10-09 20:59:39 +02:00
web_src [v1.22] [BRANDING] Add Forgejo light, dark, and auto themes 2023-10-09 20:59:22 +02:00
.air.toml Reduce verbosity of dev commands (#24917) 2023-05-24 20:11:04 +00:00
.changelog.yml Changelog for v1.15.0-rc1 (#16422) 2021-07-15 11:47:57 -04:00
.dockerignore Move public asset files to the proper directory (#25907) 2023-07-18 18:06:43 +02:00
.drone.yml Update nodejs installation method in release container (#27207) 2023-09-23 13:18:47 +00:00
.editorconfig Add markdownlint (#20512) 2022-07-28 09:22:47 +08:00
.eslintrc.yaml Update JS and PY dependencies (#27501) 2023-10-08 00:16:20 +00:00
.gitattributes [META] Use correct language for .tmpl 2023-10-09 19:11:02 +02:00
.gitignore [CI] gitignore: emacs backups 2023-10-09 18:25:29 +02: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) 2023-10-07 15:30:21 +02: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 Fix more yaml lint errors (#27284) 2023-09-26 12:56:42 -04:00
BSDmakefile update BSDmakefile to latest version from upstream (#24063) 2023-04-11 23:42:22 -04: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) (#27411) 2023-10-03 14:22:03 +00:00
CODEOWNERS [META] Add CODEOWNERS files 2023-10-09 19:11:03 +02:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-10-09 18:46:39 +02:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [BRANDING] symlink gitea to forgejo in docker containers 2023-10-09 20:59:39 +02:00
Dockerfile.rootless [BRANDING] symlink gitea to forgejo in docker containers 2023-10-09 20:59:39 +02:00
go.mod Downgrade go-co-op/gocron to v1.31.1 (#27511) 2023-10-07 18:54:02 -04:00
go.sum Downgrade go-co-op/gocron to v1.31.1 (#27511) 2023-10-07 18:54:02 -04:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-10-09 19:11:02 +02:00
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-10-09 20:59:39 +02:00
MAINTAINERS Apply to become a maintainer (#27522) 2023-10-08 10:36:40 -04:00
Makefile [BRANDING] add forgejo target to Makefile 2023-10-09 20:59:39 +02:00
package-lock.json Update JS and PY dependencies (#27501) 2023-10-08 00:16:20 +00:00
package.json Update JS and PY dependencies (#27501) 2023-10-08 00:16:20 +00: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) 2023-10-08 00:16:20 +00: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-10-09 20:59:38 +02:00
README.md [BRANDING] add Forgejo logo 2023-10-09 20:51:47 +02:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-10-09 19:11:01 +02: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 2023-10-09 19:11:02 +02:00

README.md

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.