mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-12-28 13:49:13 -05:00
e8433b7fe6
- **Installation**: includes how to install Gitea and related other tools, also includes upgrade Gitea - **Administration**: includes how to configure Gitea, customize Gitea and manage Gitea instance out of Gitea admin UI - **Usage**: includes how to use Gitea's functionalities. A sub documentation is about packages, in future we could also include CI/CD and others. - **Development**: includes how to integrate with Gitea's API, how to develop new features within Gitea - **Contributing**: includes how to contribute code to Gitea repositories. After this is merged, I think we can have a sub-documentation of `Usage` part named `Actions` to describe how to use Gitea actions --------- Co-authored-by: John Olheiser <john.olheiser@gmail.com>
36 lines
1.2 KiB
Markdown
36 lines
1.2 KiB
Markdown
---
|
|
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.
|