tdsds.com/gitea
tdsds.com/gitea
1
1
Fork 0
mirror of https://github.com/go-gitea/gitea synced 2024-11-09 11:44:27 +00:00
Code Releases Activity
cc64d4d2b2
gitea/docs/content/usage/actions/secrets.en-us.md
Giteabot 7ecb1d63bb
Move documents under actions (#31110) (#31116) 
Backport #31110 by @lunny

Move secrets and badge under actions

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
2024-05-27 23:05:49 +08:00

1.3 KiB
Raw Blame History

date title slug sidebar_position draft toc menu
2022-12-19T21:26:00+08:00 Secrets secrets 50 false false
sidebar
parent name sidebar_position identifier
actions 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+ 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.

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.