 5882e179a9
			
		
	
	5882e179a9
	
	
	
		
			
			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 <xiaolunwen@gmail.com>
		
			
				
	
	
	
		
			1.2 KiB
		
	
	
	
	
	
	
	
			
		
		
	
	| date | title | slug | draft | toc | menu | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2022-12-19T21:26:00+08:00 | Secrets | secrets/overview | false | false | 
 | 
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_andGITEA_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.