1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2025-08-05 09:55:20 +02:00

Rename develop -> development, contribute -> contributing, administer -> administration (#23662)

backport #23629 

To make versioned documentation less surprising, 1.19 should have the
same technology.
This commit is contained in:
Lunny Xiao 2023-03-24 04:44:09 +08:00 committed by GitHub
parent e7a5429d7a
commit 162f2841d0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
121 changed files with 257 additions and 342 deletions

View file

@ -0,0 +1,36 @@
---
date: "2022-12-19T21:26:00+08:00"
title: "Secrets"
slug: "usage/secrets"
draft: false
toc: false
menu:
sidebar:
parent: "usage"
name: "Secrets"
weight: 1
identifier: "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.