Beyond coding. We forge. (Code of Conduct: https://codeberg.org/forgejo/code-of-conduct)
Go to file
wxiaoguang 24a9caa2f3
Fix more HTMLURL in templates (#22831)
I haven't tested `runs_list.tmpl` but I think it could be right.

After this PR, besides the `<meta .. HTMLURL>` in html head, the only
explicit HTMLURL usage is in `pull_merge_instruction.tmpl`, which
doesn't affect users too much and it's difficult to fix at the moment.

There are still many usages of `AppUrl` in the templates (eg: the
package help manual), they are similar problems as the HTMLURL in
pull_merge_instruction, and they might be fixed together in the future.

Diff without space:
https://github.com/go-gitea/gitea/pull/22831/files?diff=unified&w=1
2023-02-09 11:31:30 -05:00
.gitea
.github
assets Use import of OCI structs (#22765) 2023-02-06 10:07:09 +00:00
build
cmd Map OIDC groups to Orgs/Teams (#21441) 2023-02-08 14:44:42 +08:00
contrib
custom/conf Add Chef package registry (#22554) 2023-02-06 09:49:21 +08:00
docker
docs Map OIDC groups to Orgs/Teams (#21441) 2023-02-08 14:44:42 +08:00
models Fix more HTMLURL in templates (#22831) 2023-02-09 11:31:30 -05:00
modules Fix more HTMLURL in templates (#22831) 2023-02-09 11:31:30 -05:00
options Map OIDC groups to Orgs/Teams (#21441) 2023-02-08 14:44:42 +08:00
public Add Chef package registry (#22554) 2023-02-06 09:49:21 +08:00
routers Map OIDC groups to Orgs/Teams (#21441) 2023-02-08 14:44:42 +08:00
services Load issue before accessing index in merge message (#22822) 2023-02-09 10:47:52 +08:00
snap
templates Fix more HTMLURL in templates (#22831) 2023-02-09 11:31:30 -05:00
tests Map OIDC groups to Orgs/Teams (#21441) 2023-02-08 14:44:42 +08:00
tools
web_src Improve AppUrl/ROOT_URL checking (#22836) 2023-02-09 11:14:45 -05:00
.air.toml
.changelog.yml
.dockerignore
.drone.yml use drone secrets for s3 config (#22770) 2023-02-05 16:42:48 -05:00
.editorconfig
.eslintrc.yaml
.gitattributes
.gitignore
.gitpod.yml
.golangci.yml
.ignore
.lgtm
.markdownlint.yaml
.npmrc
.spectral.yaml
.stylelintrc.yaml
BSDmakefile
build.go
CHANGELOG.md
CONTRIBUTING.md
DCO
Dockerfile
Dockerfile.rootless
go.mod Use import of OCI structs (#22765) 2023-02-06 10:07:09 +00:00
go.sum Use import of OCI structs (#22765) 2023-02-06 10:07:09 +00:00
LICENSE
main.go
MAINTAINERS
Makefile
package-lock.json
package.json
playwright.config.js
README.md
README_ZH.md
SECURITY.md
vitest.config.js
webpack.config.js

Gitea

Gitea - Git with a cup of tea

Contribute with Gitpod

View this document in Chinese

Purpose

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.

Building

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

The build target is split into two sub-targets:

  • make backend which requires Go Stable, required version is defined in go.mod.
  • make frontend which 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.

Parallelism (make -j <num>) is not supported.

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:

  1. YOU MUST READ THE CONTRIBUTORS GUIDE BEFORE STARTING TO WORK ON A PULL REQUEST.
  2. If you have found a vulnerability in the project, please write privately to security@gitea.io. Thanks!

Translating

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.

https://docs.gitea.io/en-us/translation-guidelines/

Crowdin

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 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.

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!

Dashboard User Profile Global Issues
Branches Web Editor Activity
New Migration Migrating Pull Request View
Pull Request Dark Diff Review Dark Diff Dark