Most of the time forks are used for contributing code only, so not having issues, projects, release and packages is a better default for such cases. They can still be enabled in the settings. A new option `DEFAULT_FORK_REPO_UNITS` is added to configure the default units on forks. Also add missing `repo.packages` unit to documentation. code by: @brechtvl ## ⚠️ BREAKING ⚠️ When forking a repository, the fork will now have issues, projects, releases, packages and wiki disabled. These can be enabled in the repository settings afterwards. To change back to the previous default behavior, configure `DEFAULT_FORK_REPO_UNITS` to be the same value as `DEFAULT_REPO_UNITS`. Co-authored-by: Brecht Van Lommel <email@example.com>
|13 hours ago|
|.gitea||1 year ago|
|.github||8 months ago|
|assets||5 days ago|
|build||6 days ago|
|cmd||3 days ago|
|contrib||4 days ago|
|custom/conf||13 hours ago|
|docker||4 days ago|
|docs||13 hours ago|
|models||13 hours ago|
|modules||13 hours ago|
|options||2 days ago|
|public||3 days ago|
|routers||17 hours ago|
|services||13 hours ago|
|snap||2 months ago|
|templates||21 hours ago|
|tests||17 hours ago|
|tools||4 weeks ago|
|web_src||17 hours ago|
|.air.toml||1 month ago|
|.changelog.yml||2 years ago|
|.dockerignore||3 months ago|
|.drone.yml||1 day ago|
|.editorconfig||6 months ago|
|.eslintrc.yaml||2 weeks ago|
|.gitattributes||4 months ago|
|.gitignore||5 months ago|
|.gitpod.yml||2 weeks ago|
|.golangci.yml||17 hours ago|
|.ignore||1 year ago|
|.lgtm||5 years ago|
|.markdownlint.yaml||6 months ago|
|.npmrc||2 years ago|
|.spectral.yaml||7 months ago|
|.stylelintrc.yaml||2 months ago|
|BSDmakefile||5 years ago|
|CHANGELOG.md||2 weeks ago|
|CONTRIBUTING.md||4 days ago|
|DCO||2 weeks ago|
|Dockerfile||1 day ago|
|Dockerfile.rootless||1 day ago|
|LICENSE||6 years ago|
|MAINTAINERS||2 months ago|
|Makefile||1 day ago|
|README.md||2 weeks ago|
|README_ZH.md||2 weeks ago|
|SECURITY.md||6 months ago|
|build.go||2 months ago|
|go.mod||1 day ago|
|go.sum||4 days ago|
|main.go||3 weeks ago|
|package-lock.json||5 days ago|
|package.json||5 days ago|
|playwright.config.js||4 months ago|
|vitest.config.js||2 months ago|
|webpack.config.js||2 months ago|
Gitea - Git with a cup of tea
The goal of this project is to make the easiest, fastest, and most painless way of setting up a self-hosted Git service.
As Gitea is written in Go, it works across all the platforms and architectures that are supported by Go, including Linux, macOS, and Windows on x86, amd64, ARM and PowerPC architectures. You can try it out using the online demo. This project has been forked from Gogs since November of 2016, but a lot has changed.
From the root of the source tree, run:
TAGS="bindata" make build
or if SQLite support is required:
TAGS="bindata sqlite sqlite_unlock_notify" make build
build target is split into two sub-targets:
make backendwhich requires Go Stable, required version is defined in go.mod.
make frontendwhich requires Node.js LTS or greater and Internet connectivity to download npm dependencies.
When building from the official source tarballs which include pre-built frontend files, the
frontend target will not be triggered, making it possible to build without Node.js and Internet connectivity.
make -j <num>) is not supported.
NOTE: If you're interested in using our APIs, we have experimental support with documentation.
Expected workflow is: Fork -> Patch -> Push -> Pull Request
- YOU MUST READ THE CONTRIBUTORS GUIDE BEFORE STARTING TO WORK ON A PULL REQUEST.
- If you have found a vulnerability in the project, please write privately to firstname.lastname@example.org. Thanks!
Translations are done through Crowdin. If you want to translate to a new language ask one of the managers in the Crowdin project to add a new language there.
You can also just create an issue for adding a language or ask on discord on the #translation channel. If you need context or find some translation issues, you can leave a comment on the string or ask on Discord. For general translation questions there is a section in the docs. Currently a bit empty but we hope to fill it as questions pop up.
For more information and instructions about how to install Gitea, please look at our documentation. If you have questions that are not covered by the documentation, you can get in contact with us on our Discord server or create a post in the discourse forum.
We maintain a list of Gitea-related projects at gitea/awesome-gitea.
The Hugo-based documentation theme is hosted at gitea/theme.
The official Gitea CLI is developed at gitea/tea.
Thank you to all our backers! 🙏 [Become a backer]
Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]
How do you pronounce Gitea?
Gitea is pronounced /ɡɪ’ti:/ as in "gi-tea" with a hard g.
Why is this not hosted on a Gitea instance?
We're working on it.
This project is licensed under the MIT License. See the LICENSE file for the full license text.
Looking for an overview of the interface? Check it out!