1
0
Fork 0
Beyond coding. We forge. https://codeberg.org/forgejo/forgejo
Find a file
cassiozareck 4d91b77d29
[FEAT] add Forgero Git Service
Signed-off-by: cassiozareck <cassiomilczareck@gmail.com>
(cherry picked from commit a878adfe62)

Adding description and Forgejo SVG

(cherry picked from commit 13738c0380)

Undo reordering and tmpl redirection

(cherry picked from commit 9ae51c46f4)
(cherry picked from commit 70fffdc61d)
(cherry picked from commit c0ebfa9da3)
(cherry picked from commit 9922c92787)
(cherry picked from commit 00c0effbc7)
(cherry picked from commit e4c9525b13)
(cherry picked from commit 09d7b83211)
(cherry picked from commit bbcd5975c9)
(cherry picked from commit 55c70a0e18)
(cherry picked from commit 76596410c0)
(cherry picked from commit 1308043931)
(cherry picked from commit 919d6aedfe)

[FEAT] add Forgero Git Service (squash) more tests

Previously only Gitea service was being tested under self-hosted migrations. Since Forgejo is also self-hosted and in fact use the same downloader/migrator we can add to this suite another test that will do the same, migrating the same repository under the same local instance but for the Forgejo service (represented by 9)

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/1709
Co-authored-by: zareck <cassiomilczareck@gmail.com>
Co-committed-by: zareck <cassiomilczareck@gmail.com>
(cherry picked from commit 40a4b8f1a8)
(cherry picked from commit 3198b4a642)
(cherry picked from commit 4edda1f389)
2023-11-27 16:16:02 +01:00
.devcontainer
.forgejo [UPGRADE] add sanity check for v1.20.5-0 2023-11-27 16:16:02 +01:00
.gitea [WORKFLOW] issues & pr templates 2023-11-27 16:10:05 +01:00
.github delete Gitea specific files that need rewriting for Forgejo 2023-11-27 16:10:03 +01:00
assets
build
cmd [CLI] implement forgejo-cli 2023-11-27 15:43:46 +01:00
contrib
custom/conf [FEAT] Use OpenStreetMap in USER_LOCATION_MAP_URL by default 2023-11-27 16:16:02 +01:00
docker
docs Fix links in docs (#28234) 2023-11-27 00:34:40 -05:00
models [UPGRADE] add sanity checks for [storage*] 2023-11-27 16:16:02 +01:00
modules [FEAT] add Forgero Git Service 2023-11-27 16:16:02 +01:00
options [FEAT] add Forgero Git Service 2023-11-27 16:16:02 +01:00
public [FEAT] add Forgero Git Service 2023-11-27 16:16:02 +01:00
releases/images [DOCS] RELEASE-NOTES.md 2023-11-27 16:15:59 +01:00
routers [API] Forgejo API /api/forgejo/v1 2023-11-27 16:16:01 +01:00
services [FEAT] add Forgero Git Service 2023-11-27 16:16:02 +01:00
snap
templates [FEAT] add Forgero Git Service 2023-11-27 16:16:02 +01:00
tests [FEAT] add Forgero Git Service 2023-11-27 16:16:02 +01:00
web_src [FEAT] add Forgero Git Service 2023-11-27 16:16:02 +01:00
.air.toml
.changelog.yml
.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 2023-11-27 16:16:01 +01:00
.gitignore [CI] gitignore: emacs backups 2023-11-27 15:44:27 +01:00
.gitpod.yml
.golangci.yml
.ignore
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
.yamllint.yaml
BSDmakefile
build.go
CHANGELOG.md
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-11-27 16:10:05 +01:00
DCO
Dockerfile [CI] Forgejo Actions based release process 2023-11-27 15:44:25 +01:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2023-11-27 15:44:25 +01:00
go.mod
go.sum
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-11-27 16:16:01 +01:00
main.go [SEMVER] store SemVer in ForgejoSemVer after a database upgrade 2023-11-27 16:16:02 +01:00
MAINTAINERS
Makefile [SEMVER] store SemVer in ForgejoSemVer after a database upgrade 2023-11-27 16:16:02 +01:00
package-lock.json Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01:00
package.json Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01: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 2023-11-27 16:10:05 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-11-27 16:15:59 +01:00
vitest.config.js
webpack.config.js [API] Forgejo API /api/forgejo/v1 2023-11-27 16:16:01 +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.