Find a file
Earl Warren 014e533206
[RELEASE] decouple the release name from the version number
The release name, as provided by FORGEJO_RELEASE, is used to build OCI
images and binary files. Although it can be the same as the Forgejo
version, it is not a requirement.

When the FORGEJO_RELEASE environment variable is set, use it as a
default for naming the binary file instead of FORGEJO_VERSION. For
instance, when building from the forgejo branch here is what is desired:

FORGEJO_VERSION=7.0.0-g2343
GITEA_VERSION=1.22.0
VERSION=vforgejo-test

The name of the release is also displayed with forgejo --version
for sanity check purposes.

Before:

FORGEJO_VERSION is the computed version
GITEA_VERSION is set manually
VERSION defaults to FORGEJO_VERSION
forgejo --help does not display VERSION

After:

FORGEJO_VERSION is the computed version
GITEA_VERSION is set manually
RELEASE_VERSION defaults to FORGEJO_VERSION
VERSION defaults to RELEASE_VERSION
forgejo --help displays VERSION
2024-02-17 15:27:35 +01:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [RELEASE] decouple the release name from the version number 2024-02-17 15:27:35 +01:00
.gitea [WORKFLOW] issues & pr templates (squash) fix link to CONTRIBUTING.md 2024-02-05 15:08:04 +01:00
assets Merge branch 'rebase-forgejo-dependency' into wip-forgejo 2024-02-05 18:58:23 +01:00
build [I18n] tooling and process 2024-02-05 15:08:04 +01:00
cmd [gitea] Fix push to create with capitalize repo name (#29090) 2024-02-10 10:53:43 +01:00
contrib Merge branch 'rebase-forgejo-dependency' into wip-forgejo 2024-02-05 18:58:23 +01:00
custom/conf Add merge style fast-forward-only (#28954) 2024-02-14 17:19:19 +01:00
docker [BRANDING] cosmetic s/Gitea/Forgejo/ in logs, messages, etc. 2024-02-05 16:02:14 +01:00
docs Add merge style fast-forward-only (#28954) 2024-02-14 17:19:19 +01:00
manual-testing@877d11b403 [TESTS] add manual testing instructions as a sub-module 2024-02-08 11:43:43 +01:00
models Refactor locale&string&template related code (#29165) 2024-02-16 15:20:52 +01:00
modules templates: HasPrefix support for template.HTML 2024-02-16 15:20:52 +01:00
options Add Zig gitignore 2024-02-15 11:19:08 +00:00
public [BRANDING] add Forgejo Git Service and migration UI 2024-02-05 16:05:02 +01:00
releases/images [DOCS] RELEASE-NOTES.md 2024-02-05 14:44:32 +01:00
routers Refactor locale&string&template related code (#29165) 2024-02-16 15:20:52 +01:00
services Refactor locale&string&template related code (#29165) 2024-02-16 15:20:52 +01:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates Merge pull request 'Add rel="nofollow" to issue filter links' (#2367) from algernon/forgejo:b/issues/nofollow into forgejo 2024-02-17 10:56:47 +00:00
tests Merge pull request 'Add rel="nofollow" to issue filter links' (#2367) from algernon/forgejo:b/issues/nofollow into forgejo 2024-02-17 10:56:47 +00:00
web_src move sign in labels to be above inputs (#28753) 2024-02-16 15:20:52 +01:00
.air.toml Reduce verbosity of dev commands (#24917) 2023-05-24 20:11:04 +00:00
.changelog.yml Adapt .changelog.yml to new labeling system (#27701) 2023-10-20 00:22:00 +02:00
.deadcode-out Refactor locale&string&template related code (#29165) 2024-02-16 15:20:52 +01:00
.dockerignore Move public asset files to the proper directory (#25907) 2023-07-18 18:06:43 +02:00
.editorconfig Add markdownlint (#20512) 2022-07-28 09:22:47 +08:00
.eslintrc.yaml Update JS and PY dependencies (#29127) 2024-02-14 21:44:24 +01:00
.gitattributes [META] Use correct language for .tmpl 2024-02-05 14:44:33 +01:00
.gitignore [DEVELOPMENT] added /local/ to .gitignore 2024-02-05 15:08:04 +01:00
.gitmodules [TESTS] add manual testing instructions as a sub-module 2024-02-08 11:43:43 +01:00
.gitpod.yml Fix Gitpod logic of setting ROOT_URL (#29162) 2024-02-16 15:20:52 +01:00
.golangci.yml [GITEA] depguard sha256-simd 2024-02-05 16:54:44 +01:00
.ignore Add /public/assets to .ignore (#26232) 2023-07-30 12:34:20 +02:00
.markdownlint.yaml Update JS dependencies (#28537) 2023-12-30 05:29:03 +00: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 and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
.yamllint.yaml fully replace drone with actions (#27556) 2023-10-11 06:39:32 +00:00
BSDmakefile Fix build errors on BSD (in BSDMakefile) (#27594) 2023-10-13 15:38:27 +00:00
build.go User/Org Feed render description as per web (#23887) 2023-04-04 04:39:47 +01:00
CHANGELOG.md Fix release link in changelog for v1.21.0 2023-11-14 15:03:49 +01:00
CODEOWNERS [META] Add CODEOWNERS files 2024-02-05 14:44:33 +01:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2024-02-05 14:44:32 +01:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [RELEASE] decouple the release name from the version number 2024-02-17 15:27:35 +01:00
Dockerfile.rootless [RELEASE] decouple the release name from the version number 2024-02-17 15:27:35 +01:00
go.mod [GITEA] Use existing error functionality 2024-02-05 16:09:40 +01:00
go.sum [GITEA] Use maintained gziphandler 2024-02-05 16:09:40 +01:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2024-02-05 14:44:32 +01:00
main.go [RELEASE] decouple the release name from the version number 2024-02-17 15:27:35 +01:00
MAINTAINERS Apply to become a maintainer (#27522) 2023-10-08 10:36:40 -04:00
Makefile [RELEASE] decouple the release name from the version number 2024-02-17 15:27:35 +01:00
package-lock.json Update JS and PY dependencies (#29127) 2024-02-14 21:44:24 +01:00
package.json Update JS and PY dependencies (#29127) 2024-02-14 21:44:24 +01: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 (#29127) 2024-02-14 21:44:24 +01:00
poetry.toml Clean up pyproject.toml and package.json, fix poetry options (#25327) 2023-06-18 18:13:08 +00:00
pyproject.toml Update JS and PY dependencies (#29127) 2024-02-14 21:44:24 +01:00
README.md [BRANDING] add Forgejo logo 2024-02-05 16:02:13 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md (squash) v1.21.5-0 (squash) go-git 2024-02-05 15:11:35 +01:00
vitest.config.js [gitea] Move vitest setup file to root (#29097) 2024-02-10 10:53:43 +01:00
webpack.config.js [gitea] Remove lightningcss (#29070) 2024-02-10 10:53:43 +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.