1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-12-25 13:19:37 -05:00
Beyond coding. We forge. (Code of Conduct: https://codeberg.org/forgejo/code-of-conduct) https://forgejo.org/
Find a file
lauralani b6aa4a40e4
[BRANDING] adapt forgejo/contrib/upgrade.sh
Reviewed at: https://codeberg.org/forgejo/forgejo/pulls/605

(cherry picked from commit ab986185d0)
(cherry picked from commit 6068aed2a7)
(cherry picked from commit 0cbd599c0c)
(cherry picked from commit c3ef135882)
(cherry picked from commit 0ba7194fa1)
(cherry picked from commit 572a2a5125)
(cherry picked from commit dd0a7265e1)
(cherry picked from commit 06bd195f4e)
(cherry picked from commit 7f6100ab6b)
(cherry picked from commit 58af04560a)
(cherry picked from commit 67a951f726)
(cherry picked from commit 46e68309ad)
(cherry picked from commit 9002654915)
(cherry picked from commit 3f1a3a1311)
(cherry picked from commit df1716deb4)
(cherry picked from commit 8ace62b413)
(cherry picked from commit 30ab21f264)
(cherry picked from commit 7ec99bfc0d)
(cherry picked from commit 47a554c9b4)
(cherry picked from commit c5aaf49d88)
(cherry picked from commit 7fb42a78a4)
(cherry picked from commit 336fd64a1f)
(cherry picked from commit a7d590f7d7)
2023-09-18 15:13:30 +02:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [TESTS] upgrade tests for storage 2023-09-18 14:11:19 +02:00
.gitea [WORKFLOW] issue template for the weekly 🔥 Forgejo furnace cleanup 2023-09-18 14:11:24 +02:00
.github delete Gitea specific files that need rewriting for Forgejo 2023-09-18 14:00:10 +02:00
assets [BRANDING] add Forgejo logo 2023-09-18 14:56:57 +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-09-18 15:13:30 +02:00
contrib [BRANDING] adapt forgejo/contrib/upgrade.sh 2023-09-18 15:13:30 +02:00
custom/conf [BRANDING] Rebrand default config settings for new installs (#140) 2023-09-18 14:56:58 +02:00
docker [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2023-09-18 15:13:26 +02:00
docs Support .git-blame-ignore-revs file (#26395) 2023-09-16 17:42:34 +00:00
models [BRANDING] reserve forgejo-actions username 2023-09-18 15:13:29 +02:00
modules [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2023-09-18 15:13:30 +02:00
options [FEAT] add Forgero Git Service 2023-09-18 14:11:24 +02:00
public [BRANDING] Custom loading animation for Forgejo 2023-09-18 14:56:58 +02:00
releases/images [DOCS] RELEASE-NOTES.md 2023-09-18 14:00:11 +02:00
routers [BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP 2023-09-18 15:13:30 +02:00
services [BRANDING] add the forgejo webhook type & update webhook docs URLs 2023-09-18 15:13:29 +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-09-18 15:13:30 +02:00
tests [BRANDING] Update nodeinfo branding 2023-09-18 15:13:29 +02:00
web_src [BRANDING] Add Forgejo light, dark, and auto themes 2023-09-18 14:56:58 +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 Add yamllint (#26965) 2023-09-07 22:24:06 -04:00
.editorconfig Add markdownlint (#20512) 2022-07-28 09:22:47 +08:00
.eslintrc.yaml Add yamllint (#26965) 2023-09-07 22:24:06 -04:00
.gitattributes [META] Use correct language for .tmpl 2023-09-18 14:00:11 +02:00
.gitignore [CI] gitignore: emacs backups 2023-09-18 13:25:12 +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 Add markdownlint (#20512) 2022-07-28 09:22:47 +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 Add yamllint (#26965) 2023-09-07 22:24:06 -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 v1.20.4 changelog (#26974) 2023-09-08 10:32:26 +00:00
CODEOWNERS [META] Add CODEOWNERS files 2023-09-18 14:11:24 +02:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-09-18 14:00:10 +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-09-18 15:13:29 +02:00
Dockerfile.rootless [BRANDING] symlink gitea to forgejo in docker containers 2023-09-18 15:13:29 +02:00
go.mod Update chroma to v2.9.1 (#26990) 2023-09-09 14:37:38 +00:00
go.sum Update chroma to v2.9.1 (#26990) 2023-09-09 14:37:38 +00:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-09-18 14:00:11 +02:00
main.go [BRANDING] alias {FORGEJO,GITEA}_{CUSTOM,WORK_DIR} 2023-09-18 15:13:29 +02:00
MAINTAINERS Apply lng2020 to maintainers (#27068) 2023-09-14 12:10:12 +08:00
Makefile [BRANDING] Replace branding in Swagger 2023-09-18 15:13:29 +02:00
package-lock.json Add missing deps to files-changed (#27100) 2023-09-16 13:23:06 +00:00
package.json Add missing deps to files-changed (#27100) 2023-09-16 13:23:06 +00:00
playwright.config.js Update JS dependencies and eslint config (#21388) 2022-10-10 20:02:20 +08:00
poetry.lock Lock yamllint and update indirect python deps (#26979) 2023-09-08 15:36:40 -04: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-09-18 15:13:26 +02:00
README.md [BRANDING] add Forgejo logo 2023-09-18 14:56:57 +02:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-09-18 14:00:11 +02:00
vitest.config.js Update JS dependencies, misc tweaks (#25768) 2023-07-08 12:26:35 +02:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2023-09-18 14:00:11 +02: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.