Go to file
zeripath 5248232c44
Try to prevent autolinking of displaynames by email readers (#19169)
Unfortunately many email readers will (helpfully) detect url or url-like names and
automatically create links to them, even in HTML emails. This is not ideal when
usernames can have dots in them.

This PR tries to prevent this behaviour by sticking ZWJ characters between dots and
also set the meta tag to prevent format detection.

Not every email template has been changed in this way - just the activation emails but
it may be that we should be setting the above meta tag in all of our emails too.

Signed-off-by: Andrew Thornton <art27@cantab.net>
2022-03-23 12:34:20 +00:00
.gitea
.github Reorder issue templates and automatically add labels (#18875) 2022-03-21 20:00:25 +08:00
assets
build
cmd Update HTTP status codes to modern codes (#18063) 2022-03-23 12:54:07 +08:00
contrib
custom/conf Add warning to set SENDMAIL_ARGS to -- (#19102) 2022-03-18 15:19:02 +01:00
docker
docs [docs] Enhance container selection in docker dump (#14292) 2022-03-22 13:50:31 +08:00
integrations Update HTTP status codes to modern codes (#18063) 2022-03-23 12:54:07 +08:00
models Fix the bug: deploy key with write access can not push (#19010) 2022-03-22 17:29:07 +08:00
modules Try to prevent autolinking of displaynames by email readers (#19169) 2022-03-23 12:34:20 +00:00
options [skip ci] Updated translations via Crowdin 2022-03-23 00:24:20 +00:00
public
routers Update HTTP status codes to modern codes (#18063) 2022-03-23 12:54:07 +08:00
services Try to prevent autolinking of displaynames by email readers (#19169) 2022-03-23 12:34:20 +00:00
snap
templates Try to prevent autolinking of displaynames by email readers (#19169) 2022-03-23 12:34:20 +00:00
tools
web_src
.air.toml
.changelog.yml
.drone.yml
.editorconfig
.eslintrc
.gitattributes
.gitignore
.golangci.yml Add 1.18 (#19151) 2022-03-21 11:22:34 +08:00
.ignore
.lgtm
.npmrc
.stylelintrc
BSDmakefile
build.go
CHANGELOG.md
CONTRIBUTING.md
DCO
Dockerfile
Dockerfile.rootless
go.mod
go.sum
jest.config.js
LICENSE
main.go
MAINTAINERS
Makefile Update tool dependencies (#19120) 2022-03-18 10:17:56 +08:00
package-lock.json
package.json
README.md
README_ZH.md
SECURITY.md
webpack.config.js

Gitea

Gitea - Git with a cup of tea

View the chinese version of this document

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 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 1.17 or greater.
  • 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 fo 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