Skip to content

Commit 4635e6d

Browse files
Runner tokens are multi use (#29153)
Fixes #28911. Co-authored-by: Giteabot <teabot@gitea.io>
1 parent 4f34691 commit 4635e6d

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

docs/content/usage/actions/act-runner.en-us.md

+2
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,8 @@ A registration token can also be obtained from the gitea [command-line interface
120120
gitea --config /etc/gitea/app.ini actions generate-runner-token
121121
```
122122

123+
Tokens are valid for registering multiple runners, until they are revoked and replaced by a new token using the token reset link in the web interface.
124+
123125
### Register the runner
124126

125127
The act runner can be registered by running the following command:

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

+2-2
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,8 @@ It is always a bad idea to use a loopback address such as `127.0.0.1` or `localh
6161
If you are unsure which address to use, the LAN address is usually the right choice.
6262

6363
`token` is used for authentication and identification, such as `P2U1U0oB4XaRCi8azcngmPCLbRpUGapalhmddh23`.
64-
It is one-time use only and cannot be used to register multiple runners.
65-
You can obtain different levels of 'tokens' from the following places to create the corresponding level of' runners':
64+
Each token can be used to create multiple runners, until it is replaced with a new token using the reset link.
65+
You can obtain different levels of 'tokens' from the following places to create the corresponding level of 'runners':
6666

6767
- Instance level: The admin settings page, like `<your_gitea.com>/admin/actions/runners`.
6868
- Organization level: The organization settings page, like `<your_gitea.com>/<org>/settings/actions/runners`.

0 commit comments

Comments
 (0)