Update meta data of docs

versioned_docs/version-1.19/usage/secrets.md

@@ -1,16 +1,7 @@
 ---
 date: "2024-07-10T09:23:00+02:00"
-title: "Secrets"
 slug: "usage/secrets"
 sidebar_position: 50
-draft: false
-toc: false
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Secrets"
-    sidebar_position: 50
-    identifier: "usage-secrets"
 ---
 
 # Secrets
@@ -18,7 +9,7 @@ menu:
 Secrets allow you to store sensitive information in your user, organization or repository.
 Secrets are available on Gitea 1.19+.
 
-# Naming your secrets
+## Naming your secrets
 
 The following rules apply to secret names:
 
@@ -34,11 +25,11 @@ The following rules apply to secret names:
 
 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.
 
-### Using secrets
+## Using secrets
 
 After creating configuration variables, they will be automatically filled in the `secrets` context.
 They can be accessed through expressions like `${{ secrets.SECRET_NAME }}` in the workflow.
 
-### Precedence
+## Precedence
 
 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.