Go to file
silverwind 3591d9bff9
Don't install playwright twice (#29302)
1. `playwright/test` is already installed as part of `deps-frontend` on
CI which runs before, so it's better to not install it again (on a
potentially different version), and just use the version from
package.json and add the `deps-frontend` dependency.
2. `PLAYWRIGHT_DIR` is a undefined variable, so I removed it

```bash
$ git show c8ded77680 | grep PLAYWRIGHT_DIR
+playwright: $(PLAYWRIGHT_DIR)
```

(cherry picked from commit c236e64aca42b9ab0743431bc505033a0cb78b93)
2024-02-26 22:30:25 +01:00
.devcontainer
.forgejo [CI] run frontend checks 2024-02-25 23:08:09 +01:00
.gitea
assets
build [FRONTEND] move the gitea svg to web_src/svg 2024-02-25 23:41:33 +01:00
cmd Revert "[BUG] Initalize Git for hook regeneration" 2024-02-26 22:30:25 +01:00
contrib
custom/conf
docker
docs
manual-testing@877d11b403
models Workaround to clean up old reviews on creating a new one (#28554) 2024-02-26 21:42:14 +01:00
modules Prevent double use of git cat-file session. (#29298) 2024-02-26 22:30:25 +01:00
options [skip ci] Updated translations via Crowdin 2024-02-26 22:30:25 +01:00
public Update Discord logo (#29285) 2024-02-26 21:42:15 +01:00
releases/images
routers Fix error display when merging PRs (#29288) 2024-02-26 22:30:25 +01:00
services Fix content size does not match error when uploading lfs file (#29259) 2024-02-26 21:42:14 +01:00
snap
templates Revert #28753 because UI broken. (#29293) 2024-02-26 22:30:25 +01:00
tests Prevent double use of git cat-file session. (#29298) 2024-02-26 22:30:25 +01:00
web_src Revert #28753 because UI broken. (#29293) 2024-02-26 22:30:25 +01:00
.air.toml
.changelog.yml
.deadcode-out
.dockerignore
.editorconfig
.eslintrc.yaml Remove jQuery .map() and enable eslint rules for it (#29272) 2024-02-26 21:42:15 +01:00
.gitattributes
.gitignore
.gitmodules
.gitpod.yml
.golangci.yml
.ignore
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
.yamllint.yaml
BSDmakefile
build.go
CHANGELOG.md
CODEOWNERS
CONTRIBUTING.md
DCO
Dockerfile
Dockerfile.rootless
go.mod
go.sum
LICENSE
main.go
MAINTAINERS
Makefile Don't install playwright twice (#29302) 2024-02-26 22:30:25 +01:00
package-lock.json [FRONTEND] package-lock.json is named as forgejo 2024-02-25 23:40:54 +01:00
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.