github-mirror/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2024-12-03 15:44:11 +08:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
83022013c8
gitea/docs/content/doc/usage/secrets.en-us.md
Lunny Xiao 67103eb2bc
Update docs markdown file weight to make it clear (#23909) 
For Docusaurus, it needs a meta data named `sidebar_position`, so we
copy all `weight` under `menu/sidebar` as top meta key.
2023-04-04 21:47:31 +08:00

1.2 KiB
Raw Blame History

date title slug weight draft toc menu
2022-12-19T21:26:00+08:00 Secrets usage/secrets 50 false false
sidebar
parent name weight identifier
usage Secrets 50 usage-secrets

Secrets

Secrets allow you to store sensitive information in your user, organization or repository.
Secrets are available on Gitea 1.19+.

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.

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.