Update meta data of docs

docs/usage/actions/variables.md

@@ -4,13 +4,13 @@ slug: "actions-variables"
 sidebar_position: 25
 ---
 
-## Variables
+# Variables
 
 You can create configuration variables on the user, organization and repository level.
 The level of the variable depends on where you created it. When creating a variable, the
 key will be converted to uppercase. You need use uppercase on the yaml file.
 
-### Naming conventions
+## Naming conventions
 
 The following rules apply to variable names:
 
@@ -21,12 +21,12 @@ The following rules apply to variable names:
 - Variable names must be unique at the level they are created at.
 - Variable names must not be `CI`.
 
-### Using variable
+## Using variable
 
 After creating configuration variables, they will be automatically filled in the `vars` context.
 They can be accessed through expressions like `${{ vars.VARIABLE_NAME }}` in the workflow.
 
-### Precedence
+## Precedence
 
 If a variable with the same name exists at multiple levels, the variable at the lowest level takes precedence:
 A repository variable will always be chosen over an organization/user variable.

docs/usage/agit-support.md

@@ -1,6 +1,5 @@
 ---
 date: "	2022-09-01T20:50:42+0000"
-title: "Agit Setup"
 slug: "agit-setup"
 sidebar_position: 12
 aliases:

docs/usage/authentication.md

@@ -1,6 +1,5 @@
 ---
 date: "2016-12-01T16:00:00+02:00"
-title: "Authentication"
 slug: "authentication"
 sidebar_position: 10
 aliases:

docs/usage/blame.md

@@ -1,6 +1,5 @@
 ---
 date: "2023-08-14T00:00:00+00:00"
-title: "Blame File View"
 slug: "blame"
 sidebar_position: 13
 aliases:

docs/usage/blocking-users.md

@@ -1,6 +1,5 @@
 ---
 date: "2024-01-31T00:00:00+00:00"
-title: "Blocking a user"
 slug: "blocking-user"
 sidebar_position: 25
 aliases:

docs/usage/clone-filter.md

@@ -1,6 +1,5 @@
 ---
 date: "2021-02-02"
-title: "Clone filters (partial clone)"
 slug: "clone-filters"
 sidebar_position: 25
 aliases:

docs/usage/code-owners.md

@@ -1,6 +1,5 @@
 ---
 date: "2023-05-24T16:00:00+00:00"
-title: "Code Owners"
 slug: "code-owners"
 sidebar_position: 30
 aliases:

docs/usage/issue-pull-request-templates.md

@@ -1,6 +1,5 @@
 ---
 date: "2018-05-10T16:00:00+02:00"
-title: "Issue and Pull Request templates"
 slug: "issue-pull-request-templates"
 sidebar_position: 15
 aliases:

docs/usage/linked-references.md

@@ -1,13 +1,12 @@
 ---
 date: "2019-11-21T17:00:00-03:00"
-title: "Automatically Linked References"
 slug: "automatically-linked-references"
 sidebar_position: 15
 aliases:
   - /en-us/automatically-linked-references
 ---
 
-# Automatically Linked References in Issues, Pull Requests and Commit Messages
+# Automatically Linked References
 
 When an issue, pull request or comment is posted, the text description is parsed
 in search for references. These references will be shown as links in the Issue View

docs/usage/merge-message-templates.md

@@ -1,6 +1,5 @@
 ---
 date: "2022-08-31T17:35:40+08:00"
-title: "Merge Message templates"
 slug: "merge-message-templates"
 sidebar_position: 15
 aliases:

docs/usage/multi-factor-authentication.md

@@ -1,6 +1,5 @@
 ---
 date: "2023-08-22T14:21:00+08:00"
-title: "Multi-factor Authentication (MFA)"
 slug: "multi-factor-authentication"
 weight: 15
 ---

docs/usage/permissions.md

@@ -1,6 +1,5 @@
 ---
 date: "2021-12-13:10:10+08:00"
-title: "Permissions"
 slug: "permissions"
 sidebar_position: 14
 aliases:

docs/usage/push.md

@@ -1,6 +1,5 @@
 ---
 date: "2020-07-06T16:00:00+02:00"
-title: "Push"
 slug: "push"
 sidebar_position: 15
 aliases:
@@ -8,9 +7,11 @@ aliases:
   - /en-us/push-options
 ---
 
+# Push
+
 There are some additional features when pushing commits to Gitea server.
 
-# Open PR through Push
+## Open PR through Push
 
 When you push commits to a non-default branch for the first time,
 you will receive a link you can click on to visit the compare page of your branch compared to your main branch.
@@ -18,12 +19,12 @@ From there, it's easy to create a pull request, even if you want to target anoth
 
 ![Gitea Push Hint](/gitea-push-hint.png)
 
-# Push Options
+## Push Options
 
 In Gitea `1.13`, support for some [push options](https://git-scm.com/docs/git-push#Documentation/git-push.txt--oltoptiongt)
 were added.
 
-## Supported Options
+### Supported Options
 
 - `repo.private` (true|false) - Change the repository's visibility.
 
@@ -37,15 +38,15 @@ Example of changing a repository's visibility to public:
 git push -o repo.private=false -u origin main
 ```
 
-# Push To Create
+## Push To Create
 
 Push to create is a feature that allows you to push to a repository that does not exist yet in Gitea. This is useful for automation and for allowing users to create repositories without having to go through the web interface. This feature is disabled by default.
 
-## Enabling Push To Create
+### Enabling Push To Create
 
 In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](../administration/config-cheat-sheet.md#repository-repository).
 
-## Using Push To Create
+### Using Push To Create
 
 Assuming you have a git repository in the current directory, you can push to a repository that does not exist yet in Gitea by running the following command: