No description
Find a file
Gusted e2d76957e5
[GITEA] Simplify cron list test (squash)
- As per
https://codeberg.org/forgejo/forgejo/pulls/1352#issuecomment-1076074
- Only test if the returned stuff is correct, not necessarily accurate.

(cherry picked from commit 55bcaf60ec)
(cherry picked from commit 4f03e48106)
(cherry picked from commit f35c31b9be)
(cherry picked from commit d08f486da2)
(cherry picked from commit 5d035c01c5)
2023-10-02 19:23:41 +02:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [TESTS] upgrade tests for storage 2023-10-02 17:06:23 +02:00
.gitea [WORKFLOW] yaml issue templates 2023-10-02 17:06:23 +02:00
.github delete Gitea specific files that need rewriting for Forgejo 2023-10-02 17:06:22 +02:00
assets
build Use Set[Type] instead of map[Type]bool/struct{}. (#26804) 2023-08-30 06:55:25 +00:00
cmd [CLI] implement forgejo-cli 2023-10-02 16:13:39 +02:00
contrib Use docs.gitea.com instead of docs.gitea.io (#26739) 2023-08-27 11:59:12 +00:00
custom/conf [GITEA] add option for banning dots in usernames 2023-10-02 19:00:59 +02:00
docker Expanded minimum RSA Keylength to 3072 (#26604) 2023-08-28 00:53:16 +00:00
docs Remove upgrade from Gogs doc because the diverse has been 7 years and the code base changed totally (#27387) 2023-10-02 14:53:55 +08:00
models [GITEA] Add slow SQL query warning 2023-10-02 19:23:41 +02:00
modules [GITEA] Add slow SQL query warning 2023-10-02 19:23:41 +02:00
options [GITEA] add option for banning dots in usernames 2023-10-02 19:00:59 +02:00
public [FEAT] add Forgero Git Service 2023-10-02 17:06:23 +02:00
releases/images [DOCS] RELEASE-NOTES.md 2023-10-02 17:06:22 +02:00
routers [GITEA] Improve HTML title on repositories 2023-10-02 19:23:24 +02:00
services [GITEA] Show manual cron run's last time 2023-10-02 19:00:59 +02:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates [GITEA] Add anchor to review types 2023-10-02 19:23:41 +02:00
tests [GITEA] Simplify cron list test (squash) 2023-10-02 19:23:41 +02:00
web_src [GITEA] Use vertical tabs on issue filters 2023-10-02 19:23:41 +02:00
.air.toml
.changelog.yml
.dockerignore
.drone.yml Update nodejs installation method in release container (#27207) 2023-09-23 13:18:47 +00:00
.editorconfig
.eslintrc.yaml Use vitest globals (#27102) 2023-09-27 04:37:13 +00:00
.gitattributes [META] Use correct language for .tmpl 2023-10-02 17:06:22 +02:00
.gitignore [CI] gitignore: emacs backups 2023-10-02 16:15:23 +02:00
.gitpod.yml
.golangci.yml Use Go 1.21 for golangci-lint (#26786) 2023-08-29 16:25:24 +02:00
.ignore
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
.yamllint.yaml Fix more yaml lint errors (#27284) 2023-09-26 12:56:42 -04:00
BSDmakefile
build.go
CHANGELOG.md Add v1.20.4 changelog (#26974) 2023-09-08 10:32:26 +00:00
CODEOWNERS [META] Add CODEOWNERS files 2023-10-02 17:06:23 +02:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-10-02 17:06:22 +02:00
DCO
Dockerfile [CI] Forgejo Actions based release process 2023-10-02 16:15:20 +02:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2023-10-02 16:15:20 +02:00
go.mod bump bleve (#27300) 2023-09-27 07:10:58 +00:00
go.sum bump bleve (#27300) 2023-09-27 07:10:58 +00:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-10-02 17:06:22 +02:00
main.go [SEMVER] store SemVer in ForgejoSemVer after a database upgrade 2023-10-02 17:06:23 +02:00
MAINTAINERS Apply lng2020 to maintainers (#27068) 2023-09-14 12:10:12 +08:00
Makefile [SEMVER] store SemVer in ForgejoSemVer after a database upgrade 2023-10-02 17:06:23 +02:00
package-lock.json Use vitest globals (#27102) 2023-09-27 04:37:13 +00:00
package.json Use vitest globals (#27102) 2023-09-27 04:37:13 +00:00
playwright.config.js
poetry.lock Update JS and Poetry dependencies and eslint (#27200) 2023-09-22 22:51:48 +02:00
poetry.toml
pyproject.toml Update JS and Poetry dependencies and eslint (#27200) 2023-09-22 22:51:48 +02:00
README.md [DOCS] README 2023-10-02 17:06:22 +02:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-10-02 17:06:22 +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-02 17:06:22 +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.