Skip to content

Commit 84033ce

Browse files
authored
1 parent 2d0ff00 commit 84033ce

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

docs/content/doc/actions/comparison.en-us.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ The missing host will be filled with `https://gitea.com` if you don't configure
132132
That means `uses: actions/checkout@v3` will download the action from [gitea.com/actions/checkout](https://gitea.com/actions/checkout), instead of [github.com/actions/checkout](https://github.com/actions/checkout).
133133

134134
As mentioned, it's configurable.
135-
If you want your runners to download actions from GitHub or your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`. See [Configuration Cheat Sheet](({{ < relref "doc/administration/config-cheat-sheet.en-us.md#actions-actions" > }})).
135+
If you want your runners to download actions from GitHub or your own Gitea instance by default, you can configure it by setting `[actions].DEFAULT_ACTIONS_URL`. See [Configuration Cheat Sheet]({{< relref "doc/administration/config-cheat-sheet.en-us.md#actions-actions" >}}).
136136

137137
### Context availability
138138

docs/content/doc/actions/quickstart.en-us.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ This page will guide you through the process of using Gitea Actions.
2424
## Set up Gitea
2525

2626
First of all, you need a Gitea instance.
27-
You can follow the [documentation]({{ < relref "doc/installation/from-package.en-us.md" > }}) to set up a new instance or upgrade your existing one.
27+
You can follow the [documentation]({{< relref "doc/installation/from-package.en-us.md" >}}) to set up a new instance or upgrade your existing one.
2828
It doesn't matter how you install or run Gitea, as long as its version is 1.19.0 or higher.
2929

3030
Actions are disabled by default, so you need to add the following to the configuration file to enable it:
@@ -34,7 +34,7 @@ Actions are disabled by default, so you need to add the following to the configu
3434
ENABLED=true
3535
```
3636

37-
If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet]({{ < relref "doc/administration/config-cheat-sheet.en-us.md#actions-actions" > }}).
37+
If you want to learn more or encounter any problems while configuring it, please refer to the [Configuration Cheat Sheet]({{< relref "doc/administration/config-cheat-sheet.en-us.md#actions-actions" >}}).
3838

3939
### Set up runner
4040

@@ -85,7 +85,7 @@ And you can see the new runner in the management page:
8585

8686
![view runner](/images/usage/actions/view-runner.png)
8787

88-
You can find more information by visiting [Act runner]({{ < relref "doc/actions/act-runner.en-us.md" > }}).
88+
You can find more information by visiting [Act runner]({{< relref "doc/actions/act-runner.en-us.md" >}}).
8989

9090
### Use Actions
9191

@@ -129,7 +129,7 @@ That is because Gitea Actions is designed to be compatible with GitHub Actions
129129
Be careful, the demo file contains some emojis.
130130
Please make sure your database supports them, especially when using MySQL.
131131
If the charset is not `utf8mb4`, errors will occur, such as `Error 1366 (HY000): Incorrect string value: '\\xF0\\x9F\\x8E\\x89 T...' for column 'name' at row 1`.
132-
See [Database Preparation]( {{ < relref "doc/installation/database-preparation.en-us.md#mysql" > }}) for more information.
132+
See [Database Preparation]({{< relref "doc/installation/database-preparation.en-us.md#mysql" >}}) for more information.
133133

134134
Alternatively, you can remove all emojis from the demo file and try again.
135135

docs/content/doc/development/hacking-on-gitea.zh-cn.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ make lint-backend
168168

169169
### 处理 JS 和 CSS
170170

171-
前端开发应遵循 [Guidelines for Frontend Development]({{ < 相关参考 "doc/development/guidelines-frontend.en-us.md" > }})
171+
前端开发应遵循 [Guidelines for Frontend Development]({{< relref "doc/contributing/guidelines-frontend.zh-cn.md" >}})
172172

173173
要使用前端资源构建,请使用上面提到的“watch-frontend”目标或只构建一次:
174174

docs/content/doc/usage/push.zh-tw.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ Push to create is a feature that allows you to push to a repository that does no
5454

5555
## Enabling Push To Create
5656

57-
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]({{ < relref "doc/administration/config-cheat-sheet.zh-tw.md#repository-repository" > }}).
57+
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]({{< relref "doc/administration/config-cheat-sheet.zh-tw.md#repository-repository" >}}).
5858

5959
## Using Push To Create
6060

0 commit comments

Comments
 (0)