Update meta data of docs

2026-09-17 19:55:34 +00:00 · 2024-08-06 16:44:42 -07:00
parent 4917bd18ae
commit af22422e1a
861 changed files with 1383 additions and 7148 deletions
@@ -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.
@@ -1,18 +1,9 @@
 ---
 date: "	2022-09-01T20:50:42+0000"
-title: "Agit Setup"
 slug: "agit-setup"
 sidebar_position: 12
-toc: false
-draft: false
 aliases:
  - /en-us/agit-setup
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Agit Setup"
-    sidebar_position: 12
-    identifier: "agit-setup"
 ---

 # Agit Setup
@@ -1,18 +1,12 @@
 ---
 date: "2016-12-01T16:00:00+02:00"
-title: "Authentication"
+
 slug: "authentication"
 sidebar_position: 10
-toc: false
-draft: false
+
 aliases:
  - /en-us/authentication
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Authentication"
-    sidebar_position: 10
-    identifier: "authentication"
+
 ---

 # Authentication
@@ -1,18 +1,9 @@
 ---
 date: "2023-08-14T00:00:00+00:00"
-title: "Blame File View"
 slug: "blame"
 sidebar_position: 13
-toc: false
-draft: false
 aliases:
  - /en-us/blame
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Blame"
-    sidebar_position: 13
-    identifier: "blame"
 ---

 # Blame File View
@@ -1,18 +1,9 @@
 ---
 date: "2024-01-31T00:00:00+00:00"
-title: "Blocking a user"
 slug: "blocking-user"
 sidebar_position: 25
-toc: false
-draft: false
 aliases:
  - /en-us/webhooks
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Blocking a user"
-    sidebar_position: 30
-    identifier: "blocking-user"
 ---

 # Blocking a user
@@ -1,18 +1,9 @@
 ---
 date: "2021-02-02"
-title: "Clone filters (partial clone)"
 slug: "clone-filters"
 sidebar_position: 25
-draft: false
-toc: false
 aliases:
  - /en-us/clone-filters
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Clone filters"
-    sidebar_position: 25
-    identifier: "clone-filters"
 ---

 # Clone filters (partial clone)
@@ -1,18 +1,9 @@
 ---
 date: "2023-05-24T16:00:00+00:00"
-title: "Code Owners"
 slug: "code-owners"
 sidebar_position: 30
-toc: false
-draft: false
 aliases:
  - /en-us/code-owners
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Code Owners"
-    sidebar_position: 30
-    identifier: "code-owners"
 ---

 # Code Owners
@@ -1,18 +1,9 @@
 ---
 date: "2022-12-01T00:00:00+00:00"
-title: "Incoming Email"
 slug: "incoming-email"
 sidebar_position: 13
-draft: false
-toc: false
 aliases:
  - /en-us/incoming-email
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Incoming Email"
-    sidebar_position: 13
-    identifier: "incoming-email"
 ---

 # Incoming Email
@@ -1,18 +1,9 @@
 ---
 date: "2018-05-10T16:00:00+02:00"
-title: "Issue and Pull Request templates"
 slug: "issue-pull-request-templates"
 sidebar_position: 15
-toc: false
-draft: false
 aliases:
  - /en-us/issue-pull-request-templates
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Issue and Pull Request templates"
-    sidebar_position: 15
-    identifier: "issue-pull-request-templates"
 ---

 # Issue and Pull Request Templates
@@ -1,18 +1,12 @@
 ---
 date: "2023-03-04T19:00:00+00:00"
-title: "Labels"
+
 slug: "labels"
 sidebar_position: 13
-toc: false
-draft: false
+
 aliases:
  - /en-us/labels
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Labels"
-    sidebar_position: 13
-    identifier: "labels"
+
 ---

 # Labels
@@ -1,21 +1,12 @@
 ---
 date: "2019-11-21T17:00:00-03:00"
-title: "Automatically Linked References"
 slug: "automatically-linked-references"
 sidebar_position: 15
-toc: false
-draft: false
 aliases:
  - /en-us/automatically-linked-references
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Automatically Linked References"
-    sidebar_position: 15
-    identifier: "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
@@ -1,10 +1,8 @@
 ---
 date: "2022-08-31T17:35:40+08:00"
-title: "Merge Message templates"
 slug: "merge-message-templates"
 sidebar_position: 15
-toc: false
-draft: false
+
 aliases:
  - /en-us/merge-message-templates
 menu:
@@ -1,16 +1,9 @@
 ---
 date: "2023-08-22T14:21:00+08:00"
-title: "Multi-factor Authentication (MFA)"
+
 slug: "multi-factor-authentication"
 weight: 15
-toc: false
-draft: false
-menu:
-  sidebar:
-    parent: "usage"
-    name: "Multi-factor Authentication (MFA)"
-    weight: 15
-    identifier: "multi-factor-authentication"
+
 ---

 # Multi-factor Authentication (MFA)
@@ -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: