Beyond coding. We forge. (Code of Conduct: https://codeberg.org/forgejo/code-of-conduct)
Go to file
Gergely Nagy d87c526d2a
Allow changing the repo Wiki branch to main
Previously, the repo wiki was hardcoded to use `master` as its branch,
this change makes it possible to use `main` (or something else, governed
by `[repository].DEFAULT_BRANCH`, a setting that already exists and
defaults to `main`).

The way it is done is that a new column is added to the `repository`
table: `wiki_branch`. The migration will make existing repositories
default to `master`, for compatibility's sake, even if they don't have a
Wiki (because it's easier to do that). Newly created repositories will
default to `[repository].DEFAULT_BRANCH` instead.

The Wiki service was updated to use the branch name stored in the
database, and fall back to the default if it is empty.

Old repositories with Wikis using the older `master` branch will have
the option to do a one-time transition to `main`, available via the
repository settings in the "Danger Zone". This option will only be
available for repositories that have the internal wiki enabled, it is
not empty, and the wiki branch is not `[repository].DEFAULT_BRANCH`.

When migrating a repository with a Wiki, Forgejo will use the same
branch name for the wiki as the source repository did. If that's not the
same as the default, the option to normalize it will be available after
the migration's done.

Additionally, the `/api/v1/{owner}/{repo}` endpoint was updated: it will
now include the wiki branch name in `GET` requests, and allow changing
the wiki branch via `PATCH`.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
2024-01-31 11:43:23 +01:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [CI] Forgejo Actions based CI for PR & branches (squash) install git >= 2.42 2024-01-28 07:47:33 +01:00
.gitea [WORKFLOW] issues & pr templates (squash) fix link to CONTRIBUTING.md 2024-01-28 08:54:31 +01:00
assets [GITEA] Use maintained gziphandler 2024-01-28 10:53:42 +01:00
build [I18n] tooling and process 2024-01-28 08:54:31 +01:00
cmd [GITEA] Refactor generation of JWT secret 2024-01-28 11:06:48 +01:00
contrib [GITEA] fix VSCode settings 2024-01-28 10:54:59 +01:00
custom/conf [GITEA] Add support for shields.io-based badges 2024-01-28 10:55:00 +01:00
docker Dockerfile small refactor (#27757) 2023-10-29 09:44:06 +08:00
docs [GITEA] Add slow SQL query warning (squash) Fix setting typo 2024-01-28 11:07:32 +01:00
models Allow changing the repo Wiki branch to main 2024-01-31 11:43:23 +01:00
modules Allow changing the repo Wiki branch to main 2024-01-31 11:43:23 +01:00
options Allow changing the repo Wiki branch to main 2024-01-31 11:43:23 +01:00
public [API] Forgejo API /api/forgejo/v1 2024-01-28 08:13:13 +01:00
releases/images [DOCS] RELEASE-NOTES.md 2024-01-28 08:13:13 +01:00
routers Allow changing the repo Wiki branch to main 2024-01-31 11:43:23 +01:00
services Allow changing the repo Wiki branch to main 2024-01-31 11:43:23 +01:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates Allow changing the repo Wiki branch to main 2024-01-31 11:43:23 +01:00
tests Allow changing the repo Wiki branch to main 2024-01-31 11:43:23 +01:00
web_src [GITEA] Use vertical tabs on issue filters 2024-01-28 09:22:15 +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 Revert "Fix schedule tasks bugs (#28691)" (part 2) 2024-01-28 11:05:33 +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 (#28120) 2023-11-20 01:02:57 +01:00
.gitattributes [META] Use correct language for .tmpl 2024-01-28 08:13:13 +01:00
.gitignore [DEVELOPMENT] added /local/ to .gitignore 2024-01-28 08:19:26 +01:00
.gitpod.yml Add Github related extensions in devcontainer (#25800) 2023-07-14 15:58:02 +08:00
.golangci.yml [GITEA] depguard sha256-simd 2024-01-28 11:07:43 +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 dependencies (#28537) 2023-12-30 05:29:03 +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-01-28 08:19:26 +01:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2024-01-28 08:13:12 +01:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [CI] Forgejo Actions based release process 2024-01-28 07:47:33 +01:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2024-01-28 07:47:33 +01:00
go.mod [GITEA] Use existing error functionality 2024-01-28 10:54:48 +01:00
go.sum [GITEA] Use maintained gziphandler 2024-01-28 10:53:42 +01:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2024-01-28 08:13:13 +01:00
main.go [SEMVER] store SemVer in ForgejoSemVer after a database upgrade 2024-01-28 08:19:25 +01:00
MAINTAINERS Apply to become a maintainer (#27522) 2023-10-08 10:36:40 -04:00
Makefile [SEMVER] 7.0.0+0-gitea-1.22.0 2024-01-28 08:54:31 +01:00
package-lock.json Revert adding htmx until we finaly decide to add it (#28879) 2024-01-21 21:42:35 +08:00
package.json Revert adding htmx until we finaly decide to add it (#28879) 2024-01-21 21:42:35 +08: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 (#28120) 2023-11-20 01:02:57 +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 (#28120) 2023-11-20 01:02:57 +01:00
README.md [DOCS] README 2024-01-28 08:13:13 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md (squash) v1.21.4-0 security 2024-01-28 08:54:31 +01: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 2024-01-28 08:13:13 +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.