aboutsummaryrefslogtreecommitdiffstats
path: root/docs/content/doc/features
diff options
context:
space:
mode:
Diffstat (limited to 'docs/content/doc/features')
-rw-r--r--docs/content/doc/features/authentication.en-us.md350
-rw-r--r--docs/content/doc/features/authentication.zh-cn.md35
-rw-r--r--docs/content/doc/features/authentication.zh-tw.md18
-rw-r--r--docs/content/doc/features/comparison.en-us.md146
-rw-r--r--docs/content/doc/features/comparison.zh-cn.md131
-rw-r--r--docs/content/doc/features/comparison.zh-tw.md132
-rw-r--r--docs/content/doc/features/localization.en-us.md33
-rw-r--r--docs/content/doc/features/localization.zh-cn.md32
-rw-r--r--docs/content/doc/features/localization.zh-tw.md32
-rw-r--r--docs/content/doc/features/webhooks.en-us.md194
-rw-r--r--docs/content/doc/features/webhooks.zh-cn.md32
-rw-r--r--docs/content/doc/features/webhooks.zh-tw.md188
12 files changed, 0 insertions, 1323 deletions
diff --git a/docs/content/doc/features/authentication.en-us.md b/docs/content/doc/features/authentication.en-us.md
deleted file mode 100644
index c27a09b00b..0000000000
--- a/docs/content/doc/features/authentication.en-us.md
+++ /dev/null
@@ -1,350 +0,0 @@
----
-date: "2016-12-01T16:00:00+02:00"
-title: "Authentication"
-slug: "authentication"
-weight: 10
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "Authentication"
- weight: 10
- identifier: "authentication"
----
-
-# Authentication
-
-{{< toc >}}
-
-## LDAP (Lightweight Directory Access Protocol)
-
-Both the LDAP via BindDN and the simple auth LDAP share the following fields:
-
-- Authorization Name **(required)**
-
- - A name to assign to the new method of authorization.
-
-- Host **(required)**
-
- - The address where the LDAP server can be reached.
- - Example: `mydomain.com`
-
-- Port **(required)**
-
- - The port to use when connecting to the server.
- - Example: `389` for LDAP or `636` for LDAP SSL
-
-- Enable TLS Encryption (optional)
-
- - Whether to use TLS when connecting to the LDAP server.
-
-- Admin Filter (optional)
-
- - An LDAP filter specifying if a user should be given administrator
- privileges. If a user account passes the filter, the user will be
- privileged as an administrator.
- - Example: `(objectClass=adminAccount)`
- - Example for Microsoft Active Directory (AD): `(memberOf=CN=admin-group,OU=example,DC=example,DC=org)`
-
-- Username attribute (optional)
-
- - The attribute of the user's LDAP record containing the user name. Given
- attribute value will be used for new Gitea account user name after first
- successful sign-in. Leave empty to use login name given on sign-in form.
- - This is useful when supplied login name is matched against multiple
- attributes, but only single specific attribute should be used for Gitea
- account name, see "User Filter".
- - Example: `uid`
- - Example for Microsoft Active Directory (AD): `sAMAccountName`
-
-- First name attribute (optional)
-
- - The attribute of the user's LDAP record containing the user's first name.
- This will be used to populate their account information.
- - Example: `givenName`
-
-- Surname attribute (optional)
-
- - The attribute of the user's LDAP record containing the user's surname.
- This will be used to populate their account information.
- - Example: `sn`
-
-- E-mail attribute **(required)**
- - The attribute of the user's LDAP record containing the user's email
- address. This will be used to populate their account information.
- - Example: `mail`
-
-### LDAP via BindDN
-
-Adds the following fields:
-
-- Bind DN (optional)
-
- - The DN to bind to the LDAP server with when searching for the user. This
- may be left blank to perform an anonymous search.
- - Example: `cn=Search,dc=mydomain,dc=com`
-
-- Bind Password (optional)
-
- - The password for the Bind DN specified above, if any. _Note: The password
- is stored encrypted with the SECRET_KEY on the server. It is still recommended
- to ensure that the Bind DN has as few privileges as possible._
-
-- User Search Base **(required)**
-
- - The LDAP base at which user accounts will be searched for.
- - Example: `ou=Users,dc=mydomain,dc=com`
-
-- User Filter **(required)**
- - An LDAP filter declaring how to find the user record that is attempting to
- authenticate. The `%s` matching parameter will be substituted with login
- name given on sign-in form.
- - Example: `(&(objectClass=posixAccount)(uid=%s))`
- - Example for Microsoft Active Directory (AD): `(&(objectCategory=Person)(memberOf=CN=user-group,OU=example,DC=example,DC=org)(sAMAccountName=%s)(!(UserAccountControl:1.2.840.113556.1.4.803:=2)))`
- - To substitute more than once, `%[1]s` should be used instead, e.g. when
- matching supplied login name against multiple attributes such as user
- identifier, email or even phone number.
- - Example: `(&(objectClass=Person)(|(uid=%[1]s)(mail=%[1]s)(mobile=%[1]s)))`
-- Enable user synchronization
- - This option enables a periodic task that synchronizes the Gitea users with
- the LDAP server. The default period is every 24 hours but that can be
- changed in the app.ini file. See the _cron.sync_external_users_ section in
- the [sample
- app.ini](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini)
- for detailed comments about that section. The _User Search Base_ and _User
- Filter_ settings described above will limit which users can use Gitea and
- which users will be synchronized. When initially run the task will create
- all LDAP users that match the given settings so take care if working with
- large Enterprise LDAP directories.
-
-### LDAP using simple auth
-
-Adds the following fields:
-
-- User DN **(required)**
-
- - A template to use as the user's DN. The `%s` matching parameter will be
- substituted with login name given on sign-in form.
- - Example: `cn=%s,ou=Users,dc=mydomain,dc=com`
- - Example: `uid=%s,ou=Users,dc=mydomain,dc=com`
-
-- User Search Base (optional)
-
- - The LDAP base at which user accounts will be searched for.
- - Example: `ou=Users,dc=mydomain,dc=com`
-
-- User Filter **(required)**
- - An LDAP filter declaring when a user should be allowed to log in. The `%s`
- matching parameter will be substituted with login name given on sign-in
- form.
- - Example: `(&(objectClass=posixAccount)(cn=%s))`
- - Example: `(&(objectClass=posixAccount)(uid=%s))`
-
-### Verify group membership in LDAP
-
-Uses the following fields:
-
-- Group Search Base (optional)
-
- - The LDAP DN used for groups.
- - Example: `ou=group,dc=mydomain,dc=com`
-
-- Group Name Filter (optional)
-
- - An LDAP filter declaring how to find valid groups in the above DN.
- - Example: `(|(cn=gitea_users)(cn=admins))`
-
-- User Attribute in Group (optional)
-
- - Which user LDAP attribute is listed in the group.
- - Example: `uid`
-
-- Group Attribute for User (optional)
- - Which group LDAP attribute contains an array above user attribute names.
- - Example: `memberUid`
-
-## PAM (Pluggable Authentication Module)
-
-This procedure enables PAM authentication. Users may still be added to the
-system manually using the user administration. PAM provides a mechanism to
-automatically add users to the current database by testing them against PAM
-authentication. To work with normal Linux passwords, the user running Gitea
-must also have read access to `/etc/shadow` in order to check the validity of
-the account when logging in using a public key.
-
-**Note**: If a user has added SSH public keys into Gitea, the use of these
-keys _may_ bypass the login check system. Therefore, if you wish to disable a user who
-authenticates with PAM, you _should_ also manually disable the account in Gitea using the
-built-in user manager.
-
-1. Configure and prepare the installation.
- - It is recommended that you create an administrative user.
- - Deselecting automatic sign-up may also be desired.
-1. Once the database has been initialized, log in as the newly created
-administrative user.
-1. Navigate to the user setting (icon in top-right corner), and select
-`Site Administration` -> `Authentication Sources`, and select
-`Add Authentication Source`.
-1. Fill out the field as follows:
- - `Authentication Type` : `PAM`
- - `Name` : Any value should be valid here, use "System Authentication" if
- you'd like.
- - `PAM Service Name` : Select the appropriate file listed under `/etc/pam.d/`
- that performs the authentication desired.[^1]
- - `PAM Email Domain` : The e-mail suffix to append to user authentication.
- For example, if the login system expects a user called `gituser`, and this
- field is set to `mail.com`, then Gitea will expect the `user email` field
- for an authenticated GIT instance to be `gituser@mail.com`.[^2]
-
-**Note**: PAM support is added via [build-time flags](https://docs.gitea.io/en-us/install-from-source/#build),
-and the official binaries provided do not have this enabled. PAM requires that
-the necessary libpam dynamic library be available and the necessary PAM
-development headers be accessible to the compiler.
-
-[^1]: For example, using standard Linux log-in on Debian "Bullseye" use
-`common-session-noninteractive` - this value may be valid for other flavors of
-Debian including Ubuntu and Mint, consult your distribution's documentation.
-[^2]: **This is a required field for PAM**. Be aware: In the above example, the
-user will log into the Gitea web interface as `gituser` and not `gituser@mail.com`
-
-## SMTP (Simple Mail Transfer Protocol)
-
-This option allows Gitea to log in to an SMTP host as a Gitea user. To
-configure this, set the fields below:
-
-- Authentication Name **(required)**
-
- - A name to assign to the new method of authorization.
-
-- SMTP Authentication Type **(required)**
-
- - Type of authentication to use to connect to SMTP host, PLAIN or LOGIN.
-
-- Host **(required)**
-
- - The address where the SMTP host can be reached.
- - Example: `smtp.mydomain.com`
-
-- Port **(required)**
-
- - The port to use when connecting to the server.
- - Example: `587`
-
-- Allowed Domains
-
- - Restrict what domains can log in if using a public SMTP host or SMTP host
- with multiple domains.
- - Example: `gitea.io,mydomain.com,mydomain2.com`
-
-- Force SMTPS
-
- - SMTPS will be used by default for connections to port 465, if you wish to use SMTPS
- for other ports. Set this value.
- - Otherwise if the server provides the `STARTTLS` extension this will be used.
-
-- Skip TLS Verify
-
- - Disable TLS verify on authentication.
-
-- This Authentication Source is Activated
- - Enable or disable this authentication source.
-
-## FreeIPA
-
-- In order to log in to Gitea using FreeIPA credentials, a bind account needs to
- be created for Gitea:
-
-- On the FreeIPA server, create a `gitea.ldif` file, replacing `dc=example,dc=com`
- with your DN, and provide an appropriately secure password:
-
- ```sh
- dn: uid=gitea,cn=sysaccounts,cn=etc,dc=example,dc=com
- changetype: add
- objectclass: account
- objectclass: simplesecurityobject
- uid: gitea
- userPassword: secure password
- passwordExpirationTime: 20380119031407Z
- nsIdleTimeout: 0
- ```
-
-- Import the LDIF (change localhost to an IPA server if needed). A prompt for
- Directory Manager password will be presented:
-
- ```sh
- ldapmodify -h localhost -p 389 -x -D \
- "cn=Directory Manager" -W -f gitea.ldif
- ```
-
-- Add an IPA group for gitea_users :
-
- ```sh
- ipa group-add --desc="Gitea Users" gitea_users
- ```
-
-- Note: For errors about IPA credentials, run `kinit admin` and provide the
- domain admin account password.
-
-- Log in to Gitea as an Administrator and click on "Authentication" under Admin Panel.
- Then click `Add New Source` and fill in the details, changing all where appropriate.
-
-## SPNEGO with SSPI (Kerberos/NTLM, for Windows only)
-
-Gitea supports SPNEGO single sign-on authentication (the scheme defined by RFC4559) for the web part of the server via the Security Support Provider Interface (SSPI) built in Windows. SSPI works only in Windows environments - when both the server and the clients are running Windows.
-
-Before activating SSPI single sign-on authentication (SSO) you have to prepare your environment:
-
-- Create a separate user account in active directory, under which the `gitea.exe` process will be running (eg. `user` under domain `domain.local`):
-
-- Create a service principal name for the host where `gitea.exe` is running with class `HTTP`:
-
- - Start `Command Prompt` or `PowerShell` as a privileged domain user (eg. Domain Administrator)
- - Run the command below, replacing `host.domain.local` with the fully qualified domain name (FQDN) of the server where the web application will be running, and `domain\user` with the name of the account created in the previous step:
-
- ```sh
- setspn -A HTTP/host.domain.local domain\user
- ```
-
-- Sign in (_sign out if you were already signed in_) with the user created
-
-- Make sure that `ROOT_URL` in the `[server]` section of `custom/conf/app.ini` is the fully qualified domain name of the server where the web application will be running - the same you used when creating the service principal name (eg. `host.domain.local`)
-
-- Start the web server (`gitea.exe web`)
-
-- Enable SSPI authentication by adding an `SPNEGO with SSPI` authentication source in `Site Administration -> Authentication Sources`
-
-- Sign in to a client computer in the same domain with any domain user (client computer, different from the server running `gitea.exe`)
-
-- If you are using Chrome or Edge, add the URL of the web app to the Local intranet sites (`Internet Options -> Security -> Local intranet -> Sites`)
-
-- Start Chrome or Edge and navigate to the FQDN URL of Gitea (eg. `http://host.domain.local:3000`)
-
-- Click the `Sign In` button on the dashboard and choose SSPI to be automatically logged in with the same user that is currently logged on to the computer
-
-- If it does not work, make sure that:
- - You are not running the web browser on the same server where Gitea is running. You should be running the web browser on a domain joined computer (client) that is different from the server. If both the client and server are running on the same computer NTLM will be preferred over Kerberos.
- - There is only one `HTTP/...` SPN for the host
- - The SPN contains only the hostname, without the port
- - You have added the URL of the web app to the `Local intranet zone`
- - The clocks of the server and client should not differ with more than 5 minutes (depends on group policy)
- - `Integrated Windows Authentication` should be enabled in Internet Explorer (under `Advanced settings`)
-
-## Reverse Proxy
-
-Gitea supports Reverse Proxy Header authentication, it will read headers as a trusted login user name or user email address. This hasn't been enabled by default, you can enable it with
-
-```ini
-[service]
-ENABLE_REVERSE_PROXY_AUTHENTICATION = true
-```
-
-The default login user name is in the `X-WEBAUTH-USER` header, you can change it via changing `REVERSE_PROXY_AUTHENTICATION_USER` in app.ini. If the user doesn't exist, you can enable automatic registration with `ENABLE_REVERSE_PROXY_AUTO_REGISTRATION=true`.
-
-The default login user email is `X-WEBAUTH-EMAIL`, you can change it via changing `REVERSE_PROXY_AUTHENTICATION_EMAIL` in app.ini, this could also be disabled with `ENABLE_REVERSE_PROXY_EMAIL`
-
-If set `ENABLE_REVERSE_PROXY_FULL_NAME=true`, a user full name expected in `X-WEBAUTH-FULLNAME` will be assigned to the user when auto creating the user. You can also change the header name with `REVERSE_PROXY_AUTHENTICATION_FULL_NAME`.
-
-You can also limit the reverse proxy's IP address range with `REVERSE_PROXY_TRUSTED_PROXIES` which default value is `127.0.0.0/8,::1/128`. By `REVERSE_PROXY_LIMIT`, you can limit trusted proxies level.
-
-Notice: Reverse Proxy Auth doesn't support the API. You still need an access token or basic auth to make API requests.
diff --git a/docs/content/doc/features/authentication.zh-cn.md b/docs/content/doc/features/authentication.zh-cn.md
deleted file mode 100644
index aeb099f760..0000000000
--- a/docs/content/doc/features/authentication.zh-cn.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-date: "2016-12-01T16:00:00+02:00"
-title: "认证"
-slug: "authentication"
-weight: 10
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "认证"
- weight: 10
- identifier: "authentication"
----
-
-# 认证
-
-## 反向代理认证
-
-Gitea 支持通过读取反向代理传递的 HTTP 头中的登录名或者 email 地址来支持反向代理来认证。默认是不启用的，你可以用以下配置启用。
-
-```ini
-[service]
-ENABLE_REVERSE_PROXY_AUTHENTICATION = true
-```
-
-默认的登录用户名的 HTTP 头是 `X-WEBAUTH-USER`，你可以通过修改 `REVERSE_PROXY_AUTHENTICATION_USER` 来变更它。如果用户不存在，可以自动创建用户，当然你需要修改 `ENABLE_REVERSE_PROXY_AUTO_REGISTRATION=true` 来启用它。
-
-默认的登录用户 Email 的 HTTP 头是 `X-WEBAUTH-EMAIL`，你可以通过修改 `REVERSE_PROXY_AUTHENTICATION_EMAIL` 来变更它。如果用户不存在，可以自动创建用户，当然你需要修改 `ENABLE_REVERSE_PROXY_AUTO_REGISTRATION=true` 来启用它。你也可以通过修改 `ENABLE_REVERSE_PROXY_EMAIL` 来启用或停用这个 HTTP 头。
-
-如果设置了 `ENABLE_REVERSE_PROXY_FULL_NAME=true`，则用户的全名会从 `X-WEBAUTH-FULLNAME` 读取，这样在自动创建用户时将使用这个字段作为用户全名，你也可以通过修改 `REVERSE_PROXY_AUTHENTICATION_FULL_NAME` 来变更 HTTP 头。
-
-你也可以通过修改 `REVERSE_PROXY_TRUSTED_PROXIES` 来设置反向代理的IP地址范围，加强安全性，默认值是 `127.0.0.0/8,::1/128`。 通过 `REVERSE_PROXY_LIMIT`， 可以设置最多信任几级反向代理。
-
-注意：反向代理认证不支持认证 API，API 仍旧需要用 access token 来进行认证。
diff --git a/docs/content/doc/features/authentication.zh-tw.md b/docs/content/doc/features/authentication.zh-tw.md
deleted file mode 100644
index da257409a2..0000000000
--- a/docs/content/doc/features/authentication.zh-tw.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-date: "2016-12-01T16:00:00+02:00"
-title: "認證"
-slug: "authentication"
-weight: 10
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "認證"
- weight: 10
- identifier: "authentication"
----
-
-# 認證
-
-## TBD
diff --git a/docs/content/doc/features/comparison.en-us.md b/docs/content/doc/features/comparison.en-us.md
deleted file mode 100644
index 5b68aed9b6..0000000000
--- a/docs/content/doc/features/comparison.en-us.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-date: "2018-05-07T13:00:00+02:00"
-title: "Gitea compared to other Git hosting options"
-slug: "comparison"
-weight: 5
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "Comparison"
- weight: 5
- identifier: "comparison"
----
-
-# Gitea compared to other Git hosting options
-
-**Table of Contents**
-
-{{< toc >}}
-
-To help decide if Gitea is suited for your needs, here is how it compares to other Git self hosted options.
-
-Be warned that we don't regularly check for feature changes in other products, so this list may be outdated. If you find anything that needs to be updated in the table below, please [open an issue](https://github.com/go-gitea/gitea/issues/new/choose).
-
-_Symbols used in table:_
-
-- _✓ - supported_
-
-- _⁄ - supported with limited functionality_
-
-- _✘ - unsupported_
-
-## General Features
-
-| Feature | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ------------------------------------------------ | --------------------------------------------------- | ---- | --------- | --------- | --------- | --------- | ------------ |
-| Open source and free | ✓ | ✓ | ✘ | ✓ | ✘ | ✘ | ✓ |
-| Low RAM/ CPU usage | ✓ | ✓ | ✘ | ✘ | ✘ | ✘ | ✘ |
-| Multiple database support | ✓ | ✓ | ✘ | ⁄ | ⁄ | ✓ | ✓ |
-| Multiple OS support | ✓ | ✓ | ✘ | ✘ | ✘ | ✘ | ✓ |
-| Easy upgrades | ✓ | ✓ | ✘ | ✓ | ✓ | ✘ | ✓ |
-| Telemetry | **✘** | ✘ | ✓ | ✓ | ✓ | ✓ | ? |
-| Third-party render tool support | ✓ | ✘ | ✘ | ✘ | ✘ | ✓ | ? |
-| WebAuthn (2FA) | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ? |
-| Extensive API | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Built-in Package/Container Registry | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Sync commits to an external repo (push mirror) | ✓ | ✓ | ✘ | ✓ | ✓ | ✘ | ✓ |
-| Sync commits from an external repo (pull mirror) | ✓ | ✘ | ✘ | ✓ | ✓ | ✘ | ? |
-| Light and Dark Theme | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ? |
-| Custom Theme Support | ✓ | ✓ | ✘ | ✘ | ✘ | ✓ | ✘ |
-| Markdown support | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| CSV support | ✓ | ✘ | ✓ | ✘ | ✘ | ✓ | ? |
-| 'GitHub / GitLab pages' | [✘](https://github.com/go-gitea/gitea/issues/302) | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Repo-specific wiki (as a repo itself) | ✓ | ✓ | ✓ | ✓ | ✓ | / | ✘ |
-| Deploy Tokens | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Repository Tokens with write rights | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| RSS Feeds | ✓ | ✘ | ✓ | ✘ | ✘ | ✘ | ✘ |
-| Built-in CI/CD | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Subgroups: groups within groups | [✘](https://github.com/go-gitea/gitea/issues/1872) | ✘ | ✘ | ✓ | ✓ | ✘ | ✓ |
-| Interaction with other instances | [/](https://github.com/go-gitea/gitea/issues/18240) | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
-| Mermaid diagrams in Markdown | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Math syntax in Markdown | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-
-## Code management
-
-| Feature | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ------------------------------------------- | --------------------------------------------------- | ---- | --------- | --------- | --------- | --------- | ------------ |
-| Repository topics | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Repository code search | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Global code search | ✓ | ✘ | ✓ | ✘ | ✓ | ✓ | ✓ |
-| Git LFS 2.0 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Group Milestones | [✘](https://github.com/go-gitea/gitea/issues/14622) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| Granular user roles (Code, Issues, Wiki, …) | ✓ | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| Verified Committer | ⁄ | ✘ | ? | ✓ | ✓ | ✓ | ✘ |
-| GPG Signed Commits | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| SSH Signed Commits | ✓ | ✘ | ✓ | ✓ | ✓ | ? | ? |
-| Reject unsigned commits | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Migrating repos from other services | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Repository Activity page | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Branch manager | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Create new branches | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Web code editor | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Commit graph | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Template Repositories | ✓ | ✘ | ✓ | ✘ | ✓ | ✓ | ✘ |
-| Git Blame | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| Visual comparison of image changes | ✓ | ✘ | ✓ | ? | ? | ? | ? |
-
-## Issue Tracker
-
-| Feature | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ----------------------------- | --------------------------------------------------- | ---- | --------- | --------- | --------- | --------- | ------------ |
-| Issue tracker | ✓ | ✓ | ✓ | ✓ | ✓ | / | ✘ |
-| Issue templates | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Labels | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Time tracking | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Multiple assignees for issues | ✓ | ✘ | ✓ | ✘ | ✓ | ✘ | ✘ |
-| Related issues | ✘ | ✘ | ⁄ | ✓ | ✓ | ✘ | ✘ |
-| Confidential issues | [✘](https://github.com/go-gitea/gitea/issues/3217) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| Comment reactions | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Lock Discussion | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Batch issue handling | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Issue Boards (Kanban) | [/](https://github.com/go-gitea/gitea/issues/14710) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| Create branch from issue | [✘](https://github.com/go-gitea/gitea/issues/20226) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| Convert comment to new issue | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Issue search | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| Global issue search | [/](https://github.com/go-gitea/gitea/issues/2434) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| Issue dependency | ✓ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
-| Create issue via email | [✘](https://github.com/go-gitea/gitea/issues/6226) | ✘ | ✘ | ✓ | ✓ | ✓ | ✘ |
-| Service Desk | [✘](https://github.com/go-gitea/gitea/issues/6219) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-
-## Pull/Merge requests
-
-| Feature | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ----------------------------------------------- | -------------------------------------------------- | ---- | --------- | --------- | --------- | --------- | ------------ |
-| Pull/Merge requests | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Squash merging | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Rebase merging | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Pull/Merge request inline comments | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Pull/Merge request approval | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Pull/Merge require approval | ✓ | ✘ | ✓ | ✘ | ✓ | ✓ | ✓ |
-| Pull/Merge multiple reviewers | ✓ | ✓ | ✓ | ✘ | ✓ | ✓ | ✓ |
-| Merge conflict resolution | [✘](https://github.com/go-gitea/gitea/issues/9014) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| Restrict push and merge access to certain users | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Revert specific commits | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| Pull/Merge requests templates | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Cherry-picking changes | ✓ | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| Download Patch | ✓ | ✘ | ✓ | ✓ | ✓ | / | ✘ |
-| Merge queues | ✘ | ✘ | ✓ | ✘ | ✓ | ✘ | ✘ |
-
-## 3rd-party integrations
-
-| Feature | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ---------------------------------------------- | ------------------------------------------------ | ---- | --------- | --------- | --------- | --------- | ------------ |
-| Webhooks | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Git Hooks | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| AD / LDAP integration | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Multiple LDAP / AD server support | ✓ | ✓ | ✘ | ✘ | ✓ | ✓ | ✓ |
-| LDAP user synchronization | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| SAML 2.0 service provider | [✘](https://github.com/go-gitea/gitea/issues/5512) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| OpenID Connect support | ✓ | ✘ | ✓ | ✓ | ✓ | ? | ✘ |
-| OAuth 2.0 integration (external authorization) | ✓ | ✘ | ⁄ | ✓ | ✓ | ? | ✓ |
-| Act as OAuth 2.0 provider | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| Two factor authentication (2FA) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| Integration with the most common services | ✓ | / | ⁄ | ✓ | ✓ | ⁄ | ✓ |
-| Incorporate external CI/CD | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
diff --git a/docs/content/doc/features/comparison.zh-cn.md b/docs/content/doc/features/comparison.zh-cn.md
deleted file mode 100644
index 55014dab7b..0000000000
--- a/docs/content/doc/features/comparison.zh-cn.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-date: "2019-02-14T11:51:04+08:00"
-title: "横向对比 Gitea 与其它 Git 托管工具"
-slug: "comparison"
-weight: 5
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "横向对比"
- weight: 5
- identifier: "comparison"
----
-
-# 横向对比 Gitea 与其它 Git 托管工具
-
-这里列出了 Gitea 与其它一些 Git 托管工具之间的异同，以便确认 Gitea 是否能够满足您的需求。
-
-请注意，此列表中的某些表项可能已经过时，因为我们并没有定期检查其它产品的功能是否有所更改。你可以前往 [Github issue](https://github.com/go-gitea/gitea/issues) 来帮助我们更新过时的内容，感谢！
-
-_表格中的符号含义:_
-
-* _✓ - 支持_
-
-* _⁄ - 部分支持_
-
-* _✘ - 不支持_
-
-* _? - 不确定_
-
-#### 主要特性
-
-| 特性 | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| --------------------- | -------------------------------------------------- | ---- | --------- | --------- | --------- | -------------- | ------------ |
-| 开源免费 | ✓ | ✓ | ✘ | ✓ | ✘ | ✘ | ✓ |
-| 低资源开销 (RAM/CPU) | ✓ | ✓ | ✘ | ✘ | ✘ | ✘ | ✘ |
-| 支持多种数据库 | ✓ | ✓ | ✘ | ⁄ | ⁄ | ✓ | ✓ |
-| 支持多种操作系统 | ✓ | ✓ | ✘ | ✘ | ✘ | ✘ | ✓ |
-| 升级简便 | ✓ | ✓ | ✘ | ✓ | ✓ | ✘ | ✓ |
-| 支持 Markdown | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 支持 Orgmode | ✓ | ✘ | ✓ | ✘ | ✘ | ✘ | ? |
-| 支持 CSV | ✓ | ✘ | ✓ | ✘ | ✘ | ✓ | ? |
-| 支持第三方渲染工具 | ✓ | ✘ | ✘ | ✘ | ✘ | ✓ | ? |
-| Git 驱动的静态 pages | [✘](https://github.com/go-gitea/gitea/issues/302) | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Git 驱动的集成化 wiki | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ (cloud only) | ✘ |
-| 部署令牌 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 仓库写权限令牌 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 内置容器 Registry | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 外部 Git 镜像 | ✓ | ✓ | ✘ | ✘ | ✓ | ✓ | ✓ |
-| WebAuthn (2FA) | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ? |
-| 内置 CI/CD | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 子组织：组织内的组织 | [✘](https://github.com/go-gitea/gitea/issues/1872) | ✘ | ✘ | ✓ | ✓ | ✘ | ✓ |
-
-#### 代码管理
-
-| 特性 | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ---------------------------------------- | ------------------------------------------------ | ---- | --------- | --------- | --------- | --------- | ------------ |
-| 仓库主题描述 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 仓库内代码搜索 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 全局代码搜索 | ✓ | ✘ | ✓ | ✘ | ✓ | ✓ | ✓ |
-| Git LFS 2.0 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 组织里程碑 | ✘ | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 细粒度用户角色 (例如 Code, Issues, Wiki) | ✓ | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 提交人的身份验证 | ⁄ | ✘ | ? | ✓ | ✓ | ✓ | ✘ |
-| GPG 签名的提交 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| SSH 签名的提交 | ✓ | ✘ | ✘ | ✘ | ✘ | ? | ? |
-| 拒绝未用通过验证的提交 | [✓](https://github.com/go-gitea/gitea/pull/9708) | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 仓库活跃度页面 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 分支管理 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 建立新分支 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 在线代码编辑 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 提交的统计图表 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 模板仓库 | [✓](https://github.com/go-gitea/gitea/pull/8768) | ✘ | ✓ | ✘ | ✓ | ✓ | ✘ |
-
-#### 工单管理
-
-| 特性 | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ------------------- | -------------------------------------------------- | --------------------------------------------- | --------- | ----------------------------------------------------------------------- | --------- | -------------- | ------------ |
-| 工单跟踪 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ (cloud only) | ✘ |
-| 工单模板 | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 标签 | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 时间跟踪 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 支持多个负责人 | ✓ | ✘ | ✓ | ✘ | ✓ | ✘ | ✘ |
-| 关联的工单 | ✘ | ✘ | ⁄ | [✓](https://docs.gitlab.com/ce/user/project/issues/related_issues.html) | ✓ | ✘ | ✘ |
-| 私密工单 | [✘](https://github.com/go-gitea/gitea/issues/3217) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 评论反馈 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 锁定讨论 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 工单批处理 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 工单看板 | [✓](https://github.com/go-gitea/gitea/pull/8346) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 从工单创建分支 | ✘ | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 工单搜索 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 工单全局搜索 | [✘](https://github.com/go-gitea/gitea/issues/2434) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 工单依赖关系 | ✓ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
-| 通过 Email 创建工单 | [✘](https://github.com/go-gitea/gitea/issues/6226) | [✘](https://github.com/gogs/gogs/issues/2602) | ✘ | ✓ | ✓ | ✓ | ✘ |
-| 服务台 | [✘](https://github.com/go-gitea/gitea/issues/6219) | ✘ | ✘ | [✓](https://gitlab.com/groups/gitlab-org/-/epics/3103) | ✓ | ✘ | ✘ |
-
-#### Pull/Merge requests
-
-| 特性 | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ------------------------------------ | -------------------------------------------------- | ---- | --------- | --------------------------------------------------------------------------------- | --------- | ------------------------------------------------------------------------ | ------------ |
-| Pull/Merge requests | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Squash merging | ✓ | ✘ | ✓ | [✓](https://docs.gitlab.com/ce/user/project/merge_requests/squash_and_merge.html) | ✓ | ✓ | ✓ |
-| Rebase merging | ✓ | ✓ | ✓ | ✘ | ⁄ | ✘ | ✓ |
-| 评论 Pull/Merge request 中的某行代码 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 指定 Pull/Merge request 的审核人 | ✓ | ✘ | ⁄ | ✓ | ✓ | ✓ | ✓ |
-| 解决 Merge 冲突 | [✘](https://github.com/go-gitea/gitea/issues/5158) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 限制某些用户的 push 和 merge 权限 | ✓ | ✘ | ✓ | ⁄ | ✓ | ✓ | ✓ |
-| 回退某些 commits 或 merge request | [✓](https://github.com/go-gitea/gitea/issues/5158) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| Pull/Merge requests 模板 | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 查看 Cherry-picking 的更改 | [✓](https://github.com/go-gitea/gitea/issues/5158) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 下载 Patch | ✓ | ✘ | ✓ | ✓ | ✓ | [/](https://jira.atlassian.com/plugins/servlet/mobile#issue/BCLOUD-8323) | ✘ |
-
-#### 第三方集成
-
-| 特性 | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| -------------------------- | -------------------------------------------------- | --------------------------------------------- | --------- | --------- | --------- | --------- | ------------ |
-| 支持 Webhook | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 自定义 Git 钩子 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 集成 AD / LDAP | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 支持多个 LDAP / AD 服务 | ✓ | ✓ | ✘ | ✘ | ✓ | ✓ | ✓ |
-| LDAP 用户同步 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| SAML 2.0 service provider | [✘](https://github.com/go-gitea/gitea/issues/5512) | [✘](https://github.com/gogs/gogs/issues/1221) | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 支持 OpenId 连接 | ✓ | ✘ | ✓ | ✓ | ✓ | ? | ✘ |
-| 集成 OAuth 2.0（外部授权） | ✓ | ✘ | ⁄ | ✓ | ✓ | ? | ✓ |
-| 作为 OAuth 2.0 provider | [✓](https://github.com/go-gitea/gitea/pull/5378) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 二次验证 (2FA) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 集成 Mattermost/Slack | ✓ | ✓ | ⁄ | ✓ | ✓ | ⁄ | ✓ |
-| 集成 Discord | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 集成 Microsoft Teams | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 显示外部 CI/CD 的状态 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
diff --git a/docs/content/doc/features/comparison.zh-tw.md b/docs/content/doc/features/comparison.zh-tw.md
deleted file mode 100644
index bde1779441..0000000000
--- a/docs/content/doc/features/comparison.zh-tw.md
+++ /dev/null
@@ -1,132 +0,0 @@
----
-date: "2018-05-07T13:00:00+02:00"
-title: "比較 Gitea 和其它自託管 Git 服務"
-slug: "comparison"
-weight: 5
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "比較"
- weight: 5
- identifier: "comparison"
----
-
-# 比較 Gitea 和其它自託管 Git 服務
-
-**目錄**
-
-{{< toc >}}
-
-為了幫助您判斷 Gitea 是否適合您的需求，這裡列出了它和其它自託管 Git 服務的比較。
-
-請注意我們不會經常檢查其它產品的功能異動，所以這份清單可能過期，如果您在下方表格中找到需要更新的資料，請在 [GitHub 的 Issue](https://github.com/go-gitea/gitea/issues) 回報。
-
-表格中使用的符號：
-
-- ✓ - 支援
-
-- ⁄ - 有限度的支援
-
-- ✘ - 不支援
-
-## 一般功能
-
-| 功能 | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ------------------------ | -------------------------------------------------- | ---- | --------- | --------- | --------- | --------- | ------------ |
-| 免費及開放原始碼 | ✓ | ✓ | ✘ | ✓ | ✘ | ✘ | ✓ |
-| 低資源使用 (RAM/CPU) | ✓ | ✓ | ✘ | ✘ | ✘ | ✘ | ✘ |
-| 支援多種資料庫 | ✓ | ✓ | ✘ | ⁄ | ⁄ | ✓ | ✓ |
-| 支援多種作業系統 | ✓ | ✓ | ✘ | ✘ | ✘ | ✘ | ✓ |
-| 簡單的升級程序 | ✓ | ✓ | ✘ | ✓ | ✓ | ✘ | ✓ |
-| 支援 Markdown | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 支援 Orgmode | ✓ | ✘ | ✓ | ✘ | ✘ | ✘ | ? |
-| 支援 CSV | ✓ | ✘ | ✓ | ✘ | ✘ | ✓ | ? |
-| 支援第三方渲染工具 | ✓ | ✘ | ✘ | ✘ | ✘ | ✓ | ? |
-| Git 驅動的靜態頁面 | [✘](https://github.com/go-gitea/gitea/issues/302) | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Git 驅動的整合 wiki | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 部署 Token | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 有寫入權限的儲存庫 Token | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✓ |
-| 內建 Container Registry | [✘](https://github.com/go-gitea/gitea/issues/2316) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 對外部 Git 鏡像 | ✓ | ✓ | ✘ | ✘ | ✓ | ✓ | ✓ |
-| FIDO (2FA) | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 內建 CI/CD | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 子群組: 群組中的群組 | ✘ | ✘ | ✘ | ✓ | ✓ | ✘ | ✓ |
-
-## 程式碼管理
-
-| 功能 | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ----------------------------------------- | ------------------------------------------------ | ---- | --------- | --------- | --------- | --------- | ------------ |
-| 儲存庫主題描述 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 儲存庫程式碼搜尋 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 全域程式碼搜尋 | ✓ | ✘ | ✓ | ✘ | ✓ | ✓ | ✓ |
-| Git LFS 2.0 | ✓ | ✘ | ✓ | ✓ | ✓ | ⁄ | ✓ |
-| 群組里程碑 | ✘ | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 精細的使用者權限（程式碼, 問題, Wiki 等） | ✓ | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 驗證提交者 | ⁄ | ✘ | ? | ✓ | ✓ | ✓ | ✘ |
-| GPG 簽署提交 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 拒絕未經簽署的提交 | [✓](https://github.com/go-gitea/gitea/pull/9708) | ✘ | ✓ | ✓ | ✓ | ✘ | ✓ |
-| 儲存庫動態頁 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 分支管理 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 建立新分支 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 網頁程式碼編輯器 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 提交線圖 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 儲存庫範本 | [✓](https://github.com/go-gitea/gitea/pull/8768) | ✘ | ✓ | ✘ | ✓ | ✓ | ✘ |
-
-## 問題追蹤器
-
-| 功能 | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| -------------------- | -------------------------------------------------- | --------------------------------------------- | --------- | ----------------------------------------------------------------------- | --------- | --------- | ------------ |
-| 問題追蹤器 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 問題範本 | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 標籤 | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 時間追蹤 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 指派問題給多個成員 | ✓ | ✘ | ✓ | ✘ | ✓ | ✘ | ✘ |
-| 相關問題 | ✘ | ✘ | ⁄ | [✓](https://docs.gitlab.com/ce/user/project/issues/related_issues.html) | ✓ | ✘ | ✘ |
-| 機密問題 | [✘](https://github.com/go-gitea/gitea/issues/3217) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 對留言的反應 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 鎖定對話 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 批次處理問題 | ✓ | ✘ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 問題看板（看板方法） | [✓](https://github.com/go-gitea/gitea/pull/8346) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 從問題建立新分支 | ✘ | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 問題搜尋 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 全域問題搜尋 | [✘](https://github.com/go-gitea/gitea/issues/2434) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 問題相依 | ✓ | ✘ | ✘ | ✘ | ✘ | ✘ | ✘ |
-| 從電子郵件建立問題 | [✘](https://github.com/go-gitea/gitea/issues/6226) | [✘](https://github.com/gogs/gogs/issues/2602) | ✘ | ✓ | ✓ | ✓ | ✘ |
-| 服務台 | [✘](https://github.com/go-gitea/gitea/issues/6219) | ✘ | ✘ | [✓](https://gitlab.com/groups/gitlab-org/-/epics/3103) | ✓ | ✘ | ✘ |
-
-## 拉取/合併請求
-
-| 功能 | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| -------------------------- | -------------------------------------------------- | ---- | --------- | --------------------------------------------------------------------------------- | --------- | ------------------------------------------------------------------------ | ------------ |
-| 拉取/合併請求 | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| Squash 合併 | ✓ | ✘ | ✓ | [✓](https://docs.gitlab.com/ce/user/project/merge_requests/squash_and_merge.html) | ✓ | ✓ | ✓ |
-| Rebase 合併 | ✓ | ✓ | ✓ | ✘ | ⁄ | ✘ | ✓ |
-| 拉取/合併請求的行內留言 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 拉取/合併請求的核可 | ✓ | ✘ | ⁄ | ✓ | ✓ | ✓ | ✓ |
-| 解決合併衝突 | [✘](https://github.com/go-gitea/gitea/issues/5158) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 限制某些使用者的推送及合併 | ✓ | ✘ | ✓ | ⁄ | ✓ | ✓ | ✓ |
-| 還原指定的提交或合併請求 | [✘](https://github.com/go-gitea/gitea/issues/5158) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 拉取/合併請求範本 | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| Cherry-picking 變更 | [✘](https://github.com/go-gitea/gitea/issues/5158) | ✘ | ✘ | ✓ | ✓ | ✘ | ✘ |
-| 下載 Patch | ✓ | ✘ | ✓ | ✓ | ✓ | [/](https://jira.atlassian.com/plugins/servlet/mobile#issue/BCLOUD-8323) | ✘ |
-
-## 第三方整合
-
-| 功能 | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
-| ------------------------- | ------------------------------------------------ | ---- | --------- | --------- | --------- | --------- | ------------ |
-| 支援 Webhook | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 自訂 Git Hook | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 整合 AD / LDAP | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| 支援多重 LDAP / AD 伺服器 | ✓ | ✓ | ✘ | ✘ | ✓ | ✓ | ✓ |
-| 同步 LDAP 使用者 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
-| SAML 2.0 service provider | [✘](https://github.com/go-gitea/gitea/issues/5512) | [✘](https://github.com/gogs/gogs/issues/1221) | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 支援 OpenId Connect | ✓ | ✘ | ✓ | ✓ | ✓ | ? | ✘ |
-| 整合 OAuth 2.0 (外部驗證) | ✓ | ✘ | ⁄ | ✓ | ✓ | ? | ✓ |
-| 成為 OAuth 2.0 提供者 | [✓](https://github.com/go-gitea/gitea/pull/5378) | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 兩步驟驗證 (2FA) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 整合 Mattermost/Slack | ✓ | ✓ | ⁄ | ✓ | ✓ | ⁄ | ✓ |
-| 整合 Discord | ✓ | ✓ | ✓ | ✓ | ✓ | ✘ | ✘ |
-| 整合 Microsoft Teams | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✘ |
-| 顯示外部 CI/CD 狀態 | ✓ | ✘ | ✓ | ✓ | ✓ | ✓ | ✓ |
diff --git a/docs/content/doc/features/localization.en-us.md b/docs/content/doc/features/localization.en-us.md
deleted file mode 100644
index e57233a622..0000000000
--- a/docs/content/doc/features/localization.en-us.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-date: "2016-12-01T16:00:00+02:00"
-title: "Localization"
-slug: "localization"
-weight: 10
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "Localization"
- weight: 20
- identifier: "localization"
----
-
-# Localization
-
-Gitea's localization happens through our [Crowdin project](https://crowdin.com/project/gitea).
-
-For changes to an **English** translation, a pull request can be made that changes the appropriate key in
-the [english locale](https://github.com/go-gitea/gitea/blob/master/options/locale/locale_en-US.ini).
-
-For changes to a **non-English** translation, refer to the Crowdin project above.
-
-## Supported Languages
-
-Any language listed in the above Crowdin project will be supported as long as 25% or more has been translated.
-
-After a translation has been accepted, it will be reflected in the main repository after the next Crowdin sync, which is generally after any PR is merged.
-
-At the time of writing, this means that a changed translation may not appear until the following Gitea release.
-
-If you use a bleeding edge build, it should appear as soon as you update after the change is synced.
diff --git a/docs/content/doc/features/localization.zh-cn.md b/docs/content/doc/features/localization.zh-cn.md
deleted file mode 100644
index dd2dc1fa90..0000000000
--- a/docs/content/doc/features/localization.zh-cn.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-date: "2016-12-01T16:00:00+02:00"
-title: "本地化"
-slug: "localization"
-weight: 10
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "本地化"
- weight: 20
- identifier: "localization"
----
-
-# 本地化
-
-Gitea的本地化是通过我们的[Crowdin项目](https://crowdin.com/project/gitea)进行的。
-
-对于对**英语翻译**的更改，可以发出pull-request，来更改[英语语言环境](https://github.com/go-gitea/gitea/blob/master/options/locale/locale_en-US.ini)中合适的关键字。
-
-有关对**非英语**翻译的更改，请参阅上面的 Crowdin 项目。
-
-## 支持的语言
-
-上述 Crowdin 项目中列出的任何语言一旦翻译了 25% 或更多都将得到支持。
-
-翻译被接受后，它将在下一次 Crowdin 同步后反映在主存储库中，这通常是在任何 PR 合并之后。
-
-在撰写本文时，这意味着更改后的翻译可能要到 Gitea 的下一个版本才会出现。
-
-如果使用开发版本，则在同步更改内容后，它应该会在更新后立即显示。
diff --git a/docs/content/doc/features/localization.zh-tw.md b/docs/content/doc/features/localization.zh-tw.md
deleted file mode 100644
index 7bb3a6e6a2..0000000000
--- a/docs/content/doc/features/localization.zh-tw.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-date: "2016-12-01T16:00:00+02:00"
-title: "在地化"
-slug: "localization"
-weight: 10
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "在地化"
- weight: 20
- identifier: "localization"
----
-
-# 在地化
-
-我們在 [Crowdin 專案](https://crowdin.com/project/gitea)上進行在地化工作。
-
-**英語系**的翻譯，可在修改[英文語言檔](https://github.com/go-gitea/gitea/blob/master/options/locale/locale_en-US.ini)後提出合併請求。
-
-**非英語系**的翻譯，請前往上述的 Crowdin 專案。
-
-## 已支援的語言
-
-上述 Crowdin 專案中列出的語言在翻譯超過 25% 後將被支援。
-
-翻譯被認可後將在下次 Crowdin 同步後進入到主儲存庫，通常是在任何合併請求被合併之後。
-
-這表示更改的翻譯要到下次 Gitea 發佈後才會出現。
-
-如果您使用的是最新建置，它將會在同步完成、您更新後出現。
diff --git a/docs/content/doc/features/webhooks.en-us.md b/docs/content/doc/features/webhooks.en-us.md
deleted file mode 100644
index ecbe13c3ad..0000000000
--- a/docs/content/doc/features/webhooks.en-us.md
+++ /dev/null
@@ -1,194 +0,0 @@
----
-date: "2016-12-01T16:00:00+02:00"
-title: "Webhooks"
-slug: "webhooks"
-weight: 10
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "Webhooks"
- weight: 30
- identifier: "webhooks"
----
-
-# Webhooks
-
-Gitea supports webhooks for repository events. This can be configured in the settings
-page `/:username/:reponame/settings/hooks` by a repository admin. Webhooks can also be configured on a per-organization and whole system basis.
-All event pushes are POST requests. The methods currently supported are:
-
-- Gitea (can also be a GET request)
-- Gogs
-- Slack
-- Discord
-- Dingtalk
-- Telegram
-- Microsoft Teams
-- Feishu
-- Wechatwork
-- Packagist
-
-### Event information
-
-**WARNING**: The `secret` field in the payload is deprecated as of Gitea 1.13.0 and will be removed in 1.14.0: https://github.com/go-gitea/gitea/issues/11755
-
-The following is an example of event information that will be sent by Gitea to
-a Payload URL:
-
-```
-X-GitHub-Delivery: f6266f16-1bf3-46a5-9ea4-602e06ead473
-X-GitHub-Event: push
-X-Gogs-Delivery: f6266f16-1bf3-46a5-9ea4-602e06ead473
-X-Gogs-Event: push
-X-Gitea-Delivery: f6266f16-1bf3-46a5-9ea4-602e06ead473
-X-Gitea-Event: push
-```
-
-```json
-{
- "secret": "3gEsCfjlV2ugRwgpU#w1*WaW*wa4NXgGmpCfkbG3",
- "ref": "refs/heads/develop",
- "before": "28e1879d029cb852e4844d9c718537df08844e03",
- "after": "bffeb74224043ba2feb48d137756c8a9331c449a",
- "compare_url": "http://localhost:3000/gitea/webhooks/compare/28e1879d029cb852e4844d9c718537df08844e03...bffeb74224043ba2feb48d137756c8a9331c449a",
- "commits": [
- {
- "id": "bffeb74224043ba2feb48d137756c8a9331c449a",
- "message": "Webhooks Yay!",
- "url": "http://localhost:3000/gitea/webhooks/commit/bffeb74224043ba2feb48d137756c8a9331c449a",
- "author": {
- "name": "Gitea",
- "email": "someone@gitea.io",
- "username": "gitea"
- },
- "committer": {
- "name": "Gitea",
- "email": "someone@gitea.io",
- "username": "gitea"
- },
- "timestamp": "2017-03-13T13:52:11-04:00"
- }
- ],
- "repository": {
- "id": 140,
- "owner": {
- "id": 1,
- "login": "gitea",
- "full_name": "Gitea",
- "email": "someone@gitea.io",
- "avatar_url": "https://localhost:3000/avatars/1",
- "username": "gitea"
- },
- "name": "webhooks",
- "full_name": "gitea/webhooks",
- "description": "",
- "private": false,
- "fork": false,
- "html_url": "http://localhost:3000/gitea/webhooks",
- "ssh_url": "ssh://gitea@localhost:2222/gitea/webhooks.git",
- "clone_url": "http://localhost:3000/gitea/webhooks.git",
- "website": "",
- "stars_count": 0,
- "forks_count": 1,
- "watchers_count": 1,
- "open_issues_count": 7,
- "default_branch": "master",
- "created_at": "2017-02-26T04:29:06-05:00",
- "updated_at": "2017-03-13T13:51:58-04:00"
- },
- "pusher": {
- "id": 1,
- "login": "gitea",
- "full_name": "Gitea",
- "email": "someone@gitea.io",
- "avatar_url": "https://localhost:3000/avatars/1",
- "username": "gitea"
- },
- "sender": {
- "id": 1,
- "login": "gitea",
- "full_name": "Gitea",
- "email": "someone@gitea.io",
- "avatar_url": "https://localhost:3000/avatars/1",
- "username": "gitea"
- }
-}
-```
-
-### Example
-
-This is an example of how to use webhooks to run a php script upon push requests to the repository.
-In your repository Settings, under Webhooks, Setup a Gitea webhook as follows:
-
-- Target URL: http://mydomain.com/webhook.php
-- HTTP Method: POST
-- POST Content Type: application/json
-- Secret: 123
-- Trigger On: Push Events
-- Active: Checked
-
-Now on your server create the php file webhook.php
-
-```
-<?php
-
-$secret_key = '123';
-
-// check for POST request
-if ($_SERVER['REQUEST_METHOD'] != 'POST') {
- error_log('FAILED - not POST - '. $_SERVER['REQUEST_METHOD']);
- exit();
-}
-
-// get content type
-$content_type = isset($_SERVER['CONTENT_TYPE']) ? strtolower(trim($_SERVER['CONTENT_TYPE'])) : '';
-
-if ($content_type != 'application/json') {
- error_log('FAILED - not application/json - '. $content_type);
- exit();
-}
-
-// get payload
-$payload = trim(file_get_contents("php://input"));
-
-if (empty($payload)) {
- error_log('FAILED - no payload');
- exit();
-}
-
-// get header signature
-$header_signature = isset($_SERVER['HTTP_X_GITEA_SIGNATURE']) ? $_SERVER['HTTP_X_GITEA_SIGNATURE'] : '';
-
-if (empty($header_signature)) {
- error_log('FAILED - header signature missing');
- exit();
-}
-
-// calculate payload signature
-$payload_signature = hash_hmac('sha256', $payload, $secret_key, false);
-
-// check payload signature against header signature
-if ($header_signature !== $payload_signature) {
- error_log('FAILED - payload signature');
- exit();
-}
-
-// convert json to array
-$decoded = json_decode($payload, true);
-
-// check for json decode errors
-if (json_last_error() !== JSON_ERROR_NONE) {
- error_log('FAILED - json decode - '. json_last_error());
- exit();
-}
-
-// success, do something
-```
-
-There is a Test Delivery button in the webhook settings that allows to test the configuration as well as a list of the most Recent Deliveries.
-
-### Authorization header
-
-**With 1.19**, Gitea hooks can be configured to send an [authorization header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization) to the webhook target.
diff --git a/docs/content/doc/features/webhooks.zh-cn.md b/docs/content/doc/features/webhooks.zh-cn.md
deleted file mode 100644
index 76139460c0..0000000000
--- a/docs/content/doc/features/webhooks.zh-cn.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-date: "2016-12-01T16:00:00+02:00"
-title: "Webhooks"
-slug: "webhooks"
-weight: 10
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "Webhooks"
- weight: 30
- identifier: "webhooks"
----
-
-# Webhooks
-
-Gitea 的存储 webhook。这可以有存储库管路设定页 `/:username/:reponame/settings/hooks` 中的。Webhook 也可以按照组织调整或全系统调整，所有时间的推送都是POST请求
-。此方法目前被下列服务支援：
-
-- Gitea (也可以是 GET 請求)
-- Gogs
-- Slack
-- Discord
-- Dingtalk
-- Telegram
-- Microsoft Teams
-- Feishu
-- Wechatwork
-- Packagist
-
-## TBD
diff --git a/docs/content/doc/features/webhooks.zh-tw.md b/docs/content/doc/features/webhooks.zh-tw.md
deleted file mode 100644
index 20fec3d62d..0000000000
--- a/docs/content/doc/features/webhooks.zh-tw.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-date: "2016-12-01T16:00:00+02:00"
-title: "Webhook"
-slug: "webhooks"
-weight: 10
-toc: false
-draft: false
-menu:
- sidebar:
- parent: "features"
- name: "Webhook"
- weight: 30
- identifier: "webhooks"
----
-
-# Webhook
-
-Gitea 的儲存庫事件支援 web hook。這可以有儲存庫管理員在設定頁 `/:username/:reponame/settings/hooks` 中調整。Webhook 也可以按照組織調整或按照全系統調整。
-所有的事件推送都是 POST 請求。此方法目前被下列服務支援：
-
-- Gitea (也可以是 GET 請求)
-- Gogs
-- Slack
-- Discord
-- Dingtalk
-- Telegram
-- Microsoft Teams
-- Feishu
-- Wechatwork
-- Packagist
-
-### 事件資訊
-
-**警告**： Payload 中的 `secret` 欄位已經在 Gitea 1.13.0 棄用，並且將在 1.14.0 移除： https://github.com/go-gitea/gitea/issues/11755
-
-下面是一個將由 Gitea 發送到 Payload URL 的事件資訊的範例：
-
-```
-X-GitHub-Delivery: f6266f16-1bf3-46a5-9ea4-602e06ead473
-X-GitHub-Event: push
-X-Gogs-Delivery: f6266f16-1bf3-46a5-9ea4-602e06ead473
-X-Gogs-Event: push
-X-Gitea-Delivery: f6266f16-1bf3-46a5-9ea4-602e06ead473
-X-Gitea-Event: push
-```
-
-```json
-{
- "secret": "3gEsCfjlV2ugRwgpU#w1*WaW*wa4NXgGmpCfkbG3",
- "ref": "refs/heads/develop",
- "before": "28e1879d029cb852e4844d9c718537df08844e03",
- "after": "bffeb74224043ba2feb48d137756c8a9331c449a",
- "compare_url": "http://localhost:3000/gitea/webhooks/compare/28e1879d029cb852e4844d9c718537df08844e03...bffeb74224043ba2feb48d137756c8a9331c449a",
- "commits": [
- {
- "id": "bffeb74224043ba2feb48d137756c8a9331c449a",
- "message": "Webhooks Yay!",
- "url": "http://localhost:3000/gitea/webhooks/commit/bffeb74224043ba2feb48d137756c8a9331c449a",
- "author": {
- "name": "Gitea",
- "email": "someone@gitea.io",
- "username": "gitea"
- },
- "committer": {
- "name": "Gitea",
- "email": "someone@gitea.io",
- "username": "gitea"
- },
- "timestamp": "2017-03-13T13:52:11-04:00"
- }
- ],
- "repository": {
- "id": 140,
- "owner": {
- "id": 1,
- "login": "gitea",
- "full_name": "Gitea",
- "email": "someone@gitea.io",
- "avatar_url": "https://localhost:3000/avatars/1",
- "username": "gitea"
- },
- "name": "webhooks",
- "full_name": "gitea/webhooks",
- "description": "",
- "private": false,
- "fork": false,
- "html_url": "http://localhost:3000/gitea/webhooks",
- "ssh_url": "ssh://gitea@localhost:2222/gitea/webhooks.git",
- "clone_url": "http://localhost:3000/gitea/webhooks.git",
- "website": "",
- "stars_count": 0,
- "forks_count": 1,
- "watchers_count": 1,
- "open_issues_count": 7,
- "default_branch": "master",
- "created_at": "2017-02-26T04:29:06-05:00",
- "updated_at": "2017-03-13T13:51:58-04:00"
- },
- "pusher": {
- "id": 1,
- "login": "gitea",
- "full_name": "Gitea",
- "email": "someone@gitea.io",
- "avatar_url": "https://localhost:3000/avatars/1",
- "username": "gitea"
- },
- "sender": {
- "id": 1,
- "login": "gitea",
- "full_name": "Gitea",
- "email": "someone@gitea.io",
- "avatar_url": "https://localhost:3000/avatars/1",
- "username": "gitea"
- }
-}
-```
-
-### 範例
-
-此範例示範在發生推送事件時，如何使用 webhook 觸發 php 程式。
-使用下列參數在您的儲存庫設定 Webhook 中建立一個 Gitea webhook：
-
-- 目標 URL： http://mydomain.com/webhook.php
-- HTTP 請求方法：POST
-- POST Content Type：application/json
-- Secret：123
-- 觸發條件：推送事件
-- 啟用：勾選
-
-現在請到您的伺服器上建立 webhook.php 檔案
-
-```
-<?php
-
-$secret_key = '123';
-
-// check for POST request
-if ($_SERVER['REQUEST_METHOD'] != 'POST') {
- error_log('FAILED - not POST - '. $_SERVER['REQUEST_METHOD']);
- exit();
-}
-
-// get content type
-$content_type = isset($_SERVER['CONTENT_TYPE']) ? strtolower(trim($_SERVER['CONTENT_TYPE'])) : '';
-
-if ($content_type != 'application/json') {
- error_log('FAILED - not application/json - '. $content_type);
- exit();
-}
-
-// get payload
-$payload = trim(file_get_contents("php://input"));
-
-if (empty($payload)) {
- error_log('FAILED - no payload');
- exit();
-}
-
-// get header signature
-$header_signature = isset($_SERVER['HTTP_X_GITEA_SIGNATURE']) ? $_SERVER['HTTP_X_GITEA_SIGNATURE'] : '';
-
-if (empty($header_signature)) {
- error_log('FAILED - header signature missing');
- exit();
-}
-
-// calculate payload signature
-$payload_signature = hash_hmac('sha256', $payload, $secret_key, false);
-
-// check payload signature against header signature
-if ($header_signature !== $payload_signature) {
- error_log('FAILED - payload signature');
- exit();
-}
-
-// convert json to array
-$decoded = json_decode($payload, true);
-
-// check for json decode errors
-if (json_last_error() !== JSON_ERROR_NONE) {
- error_log('FAILED - json decode - '. json_last_error());
- exit();
-}
-
-// success, do something
-```
-
-Webhook 設定中有一個傳送測試資料按鈕，它可讓你測試您的設定並將結果顯示於最近傳送記錄。
generated by cgit v1.2.3 (git 2.39.1) at 2025-05-08 13:49:05 +0000