You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes#22183
Replaces #22187
This PR adds secrets for users. I refactored the files for organizations
and repos to use the same logic and templates. I splitted the secrets
from deploy keys again and reverted the fix from #22187.
---------
Co-authored-by: Lunny Xiao <[email protected]>
Copy file name to clipboardExpand all lines: docs/content/doc/secrets/overview.en-us.md
+8-8
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
date: "2022-12-19T21:26:00+08:00"
3
-
title: "Encrypted secrets"
3
+
title: "Secrets"
4
4
slug: "secrets/overview"
5
5
draft: false
6
6
toc: false
@@ -12,24 +12,24 @@ menu:
12
12
identifier: "overview"
13
13
---
14
14
15
-
# Encrypted secrets
15
+
# Secrets
16
16
17
-
Encrypted secrets allow you to store sensitive information in your organization or repository.
17
+
Secrets allow you to store sensitive information in your user, organization or repository.
18
18
Secrets are available on Gitea 1.19+.
19
19
20
20
# Naming your secrets
21
21
22
22
The following rules apply to secret names:
23
23
24
-
Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
24
+
-Secret names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
25
25
26
-
Secret names must not start with the `GITHUB_` and `GITEA_` prefix.
26
+
-Secret names must not start with the `GITHUB_` and `GITEA_` prefix.
27
27
28
-
Secret names must not start with a number.
28
+
-Secret names must not start with a number.
29
29
30
-
Secret names are not case-sensitive.
30
+
-Secret names are not case-sensitive.
31
31
32
-
Secret names must be unique at the level they are created at.
32
+
-Secret names must be unique at the level they are created at.
33
33
34
34
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.
0 commit comments