2022-12-20 09:07:13 +00:00
---
date: "2022-12-19T21:26:00+08:00"
2023-02-01 12:53:04 +00:00
title: "Secrets"
2023-03-23 15:18:24 +00:00
slug: "usage/secrets"
2023-04-04 13:47:31 +00:00
weight: 50
2022-12-20 09:07:13 +00:00
draft: false
toc: false
menu:
sidebar:
2023-03-23 15:18:24 +00:00
parent: "usage"
name: "Secrets"
2023-04-04 13:47:31 +00:00
weight: 50
2023-03-23 15:18:24 +00:00
identifier: "usage-secrets"
2022-12-20 09:07:13 +00:00
---
2023-02-01 12:53:04 +00:00
# Secrets
2022-12-20 09:07:13 +00:00
2023-02-01 12:53:04 +00:00
Secrets allow you to store sensitive information in your user, organization or repository.
2022-12-20 09:07:13 +00:00
Secrets are available on Gitea 1.19+.
# Naming your secrets
The following rules apply to secret names:
2023-02-01 12:53:04 +00:00
- Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]` , `[0-9]` ) or underscores (`_`). Spaces are not allowed.
2022-12-20 09:07:13 +00:00
2023-02-01 12:53:04 +00:00
- Secret names must not start with the `GITHUB_` and `GITEA_` prefix.
2022-12-20 09:07:13 +00:00
2023-02-01 12:53:04 +00:00
- Secret names must not start with a number.
2022-12-20 09:07:13 +00:00
2023-02-01 12:53:04 +00:00
- Secret names are not case-sensitive.
2022-12-20 09:07:13 +00:00
2023-02-01 12:53:04 +00:00
- Secret names must be unique at the level they are created at.
2022-12-20 09:07:13 +00: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.
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.
