2022-12-20 17:07:13 +08:00
---
2024-07-12 15:25:32 +00:00
date : "2024-07-10T09:23:00+02:00"
2023-04-27 22:33:41 -05:00
slug : "secrets"
2023-07-25 23:53:13 -05:00
sidebar_position : 50
2022-12-20 17:07:13 +08:00
---
2023-02-01 13:53:04 +01:00
# Secrets
2022-12-20 17:07:13 +08:00
2023-02-01 13:53:04 +01:00
Secrets allow you to store sensitive information in your user, organization or repository.
2023-07-24 22:39:10 +08:00
Secrets are available on Gitea 1.19+ and are only visible in 1.20+ when ACTIONS are enabled.
2022-12-20 17:07:13 +08:00
# Naming your secrets
The following rules apply to secret names:
2023-02-01 13:53:04 +01:00
- Secret names can only contain alphanumeric characters (`[a-z]` , `[A-Z]` , `[0-9]` ) or underscores (`_` ). Spaces are not allowed.
2022-12-20 17:07:13 +08:00
2023-02-01 13:53:04 +01:00
- Secret names must not start with the `GITHUB_` and `GITEA_` prefix.
2022-12-20 17:07:13 +08:00
2023-02-01 13:53:04 +01:00
- Secret names must not start with a number.
2022-12-20 17:07:13 +08:00
2023-02-01 13:53:04 +01:00
- Secret names are not case-sensitive.
2022-12-20 17:07:13 +08:00
2023-02-01 13:53:04 +01:00
- Secret names must be unique at the level they are created at.
2022-12-20 17:07:13 +08:00
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.
2024-07-12 15:25:32 +00:00
### 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
2022-12-20 17:07:13 +08:00
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.
