docs: add zh-tw folder (#195)

Signed-off-by: appleboy <[email protected]> Reviewed-on: https://gitea.com/gitea/docs/pulls/195 Reviewed-by: Lunny Xiao <[email protected]> Co-authored-by: appleboy <[email protected]> Co-committed-by: appleboy <[email protected]>
2026-09-17 19:55:34 +00:00 · 2025-04-04 23:28:16 +00:00
parent 3275094871
commit dbfa0ba454
835 changed files with 72590 additions and 5155 deletions
@@ -0,0 +1,35 @@
+---
+date: "2024-07-10T09:23:00+02:00"
+slug: "secrets"
+sidebar_position: 50
+---
+
+# Secrets
+
+Secrets allow you to store sensitive information in your user, organization or repository.
+Secrets are available on Gitea 1.19+ and are only visible in 1.20+ when ACTIONS are enabled.
+
+# Naming your secrets
+
+The following rules apply to secret names:
+
+- Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
+
+- Secret names must not start with the `GITHUB_` and `GITEA_` prefix.
+
+- Secret names must not start with a number.
+
+- Secret names are not case-sensitive.
+
+- Secret names must be unique at the level they are created at.
+
+For example, a secret created at the repository level must have a unique name in that repository, and a secret created at the organization level must have a unique name at that level.
+
+### Using secrets
+
+After creating configuration variables, they will be automatically filled in the `secrets` context.
+They can be accessed through expressions like `${{ secrets.SECRET_NAME }}` in the workflow.
+
+### Precedence
+
+If a secret with the same name exists at multiple levels, the secret at the lowest level takes precedence. For example, if an organization-level secret has the same name as a repository-level secret, then the repository-level secret takes precedence.