gitea/gitea-docs
1
0
Fork 0
mirror of https://gitea.com/gitea/docs.git synced 2026-07-09 06:55:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update zh tw languages and fix some broken links

Browse Source
This commit is contained in:
Lunny Xiao
2026-07-01 14:47:51 -07:00
parent 9558006c39
commit a084bdb556
842 changed files with 31137 additions and 31065 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
versioned_docs/version-1.27/usage/actions/runner.mdx
View File

@@ -59,7 +59,7 @@ If you cannot see the settings page, please make sure that you have the right pe
The format of the registration token is a random string `D0gvfu2iHfUjNqCYVljVyRV14fISpJxxxxxxxxxx`.
A registration token can also be obtained from the Gitea [command-line interface](../../administration/command-line.md#actions-generate-runner-token):
A registration token can also be obtained from the Gitea [command-line interface](/administration/command-line#actions-generate-runner-token):
```
gitea --config /etc/gitea/app.ini actions generate-runner-token

2
versioned_docs/version-1.27/usage/actions/token-permissions.md
View File

@@ -9,7 +9,7 @@ sidebar_position: 30
Every Actions job receives a built-in token (`GITEA_TOKEN`) which can be used to access Gitea (Git over HTTP(S), API requests, etc.).
This page documents how Gitea decides what the token is allowed to do.
In workflows, it is available as `${{ secrets.GITEA_TOKEN }}`. These settings and `permissions:` only affect `GITEA_TOKEN` (not other secrets like personal access tokens). For API calls, see [API authentication](../../development/api-usage.md#authentication).
In workflows, it is available as `${{ secrets.GITEA_TOKEN }}`. These settings and `permissions:` only affect `GITEA_TOKEN` (not other secrets like personal access tokens). For API calls, see [API authentication](development/api-usage.md).
## Where permissions come from