linden123/githaven-fork
1
1
Fork 0
forked from Shiloh/githaven
Code Pull Requests Activity
acc74c2fc6
githaven-fork/docs/content/doc/usage/secrets.en-us.md
JonRB acc74c2fc6
Update secrets.en-us.md (#26057) 
Present documentation does not capture that secrets are only visible if
ACTIONS are enabled for a repository. This PR adds a short note
2023-07-22 09:34:01 +00:00

1.3 KiB
Raw Blame History

date title slug weight draft toc aliases menu
2022-12-19T21:26:00+08:00 Secrets secrets 50 false false
/en-us/secrets
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+ 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.