44d6a904d3
We're working on rolling out gitea as a replacement for a fairly large cgit installation. Part of this involves a metric ton of mod_rewrite rules so that links people have out in the wild will still work. Unfortunately, cgit uses #n1 in the url to indicate a single line highlight, which doesn't get passed to the server and therefore can't be rewritten. We've got a local workaround by shoving a script block into a custom header template, but thought it might be nicer to upstream a simple patch to support #n as a prefix for single line highlights. (luckily for simplicity, cgit does not support ranges) Signed-off-by: Monty Taylor <mordred@inaugust.com> |
||
|---|---|---|
| .github | ||
| assets | ||
| cmd | ||
| contrib | ||
| custom/conf | ||
| docker | ||
| docs | ||
| integrations | ||
| models | ||
| modules | ||
| options | ||
| public | ||
| routers | ||
| scripts | ||
| snap | ||
| templates | ||
| vendor | ||
| .changelog.yml | ||
| .drone.yml | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .lgtm | ||
| .revive.toml | ||
| BSDmakefile | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| DCO | ||
| Dockerfile | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE | ||
| main.go | ||
| MAINTAINERS | ||
| Makefile | ||
| package-lock.json | ||
| package.json | ||
| README_ZH.md | ||
| README.md | ||
Gitea - Git with a cup of tea
Purpose
The goal of this project is to make the easiest, fastest, and most
painless way of setting up a self-hosted Git service.
Using Go, this can be done with an independent binary distribution across
all platforms which Go supports, including Linux, macOS, and Windows
on x86, amd64, ARM and PowerPC architectures.
Want to try it before doing anything else?
Do it with the online demo!
This project has been
forked from
Gogs since 2016.11 but changed a lot.
Building
From the root of the source tree, run:
TAGS="bindata" make generate all
More info: https://docs.gitea.io/en-us/install-from-source/
Using
./gitea web
NOTE: If you're interested in using our APIs, we have experimental
support with documentation.
Contributing
Expected workflow is: Fork -> Patch -> Push -> Pull Request
NOTES:
- 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 security@gitea.io. Thanks!
Further information
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 forum!
Authors
Backers
Thank you to all our backers! 🙏 [Become a backer]
Sponsors
Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]
FAQ
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.
License
This project is licensed under the MIT License.
See the LICENSE file
for the full license text.
Screenshots
Looking for an overview of the interface? Check it out!
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |