MarcoBuster/gitea
1
0
Fork 0
mirror of https://github.com/go-gitea/gitea synced 2024-12-22 15:27:54 +01:00
Code Issues Packages Projects Releases Wiki Activity
release/v1.19
gitea/docs/content/usage/secrets.en-us.md
John Olheiser 8c771c8b91
Docusaurus-ify 1.19 (#26053) 
See https://github.com/go-gitea/gitea/pull/26051

---------

Signed-off-by: jolheiser <john.olheiser@gmail.com>
Co-authored-by: Giteabot <teabot@gitea.io>
2023-07-26 10:01:15 +08:00

1.2 KiB
Raw Permalink Blame History

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