You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/usage/actions/act-runner.en-us.md
+15-12
Original file line number
Diff line number
Diff line change
@@ -245,7 +245,8 @@ You can find more useful images on [act images](https://github.com/nektos/act/bl
245
245
If you want to run jobs in the host directly, you can change it to `ubuntu-22.04:host` or just `ubuntu-22.04`, the `:host` is optional.
246
246
However, we suggest you to use a special name like `linux_amd64:host` or `windows:host` to avoid misusing it.
247
247
248
-
After Gitea 1.21 released, you can change labels by modfiying `container.labels` in configuration file (if you don't have a configuration file, please refer to [configuration tutorials](#configuration)), and runner will declare the new labels which you defined in configuration file after executing `./act_runner daemon --config config.yaml`.
248
+
Starting with Gitea 1.21, you can change labels by modifying `container.labels` in the runner configuration file (if you don't have a configuration file, please refer to [configuration tutorials](#configuration)).
249
+
The runner will use these new labels as soon as you restart it, i.e., by calling `./act_runner daemon --config config.yaml`.
249
250
250
251
## Running
251
252
@@ -263,29 +264,31 @@ Since act runner is still in development, it is recommended to check the latest
263
264
264
265
## Configuration variable
265
266
266
-
You can create configuration varibales with user, organization, repository level. And the level of the variable depends on which setting panel you created in.
267
+
You can create configuration variables on the user, organization and repository level.
268
+
The level of the variable depends on where you created it.
267
269
268
270
### Naming conventions
269
271
270
272
The following rules apply to variable names:
271
273
272
-
- Varibale names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
274
+
- Variable names can only contain alphanumeric characters (`[a-z]`, `[A-Z]`, `[0-9]`) or underscores (`_`). Spaces are not allowed.
273
275
274
-
- Varibale names must not start with the `GITHUB_` and `GITEA_` prefix.
276
+
- Variable names must not start with the `GITHUB_` and `GITEA_` prefix.
275
277
276
-
- Varibale names must not start with a number.
278
+
- Variable names must not start with a number.
277
279
278
-
- Varibale names are not case-sensitive.
280
+
- Variable names are case-insensitive.
279
281
280
-
- Varibale names must be unique at the level they are created at.
282
+
- Variable names must be unique at the level they are created at.
281
283
282
-
- Varibale names must not be 'CI'.
284
+
- Variable names must not be `CI`.
283
285
284
-
### Using varibales
286
+
### Using variable
285
287
286
-
After creating configuration varibales, they will be automatically filled in the `vars` context. They are available to you with expression like `{{ vars.VARIABLE_NAME }}` in workflow.
288
+
After creating configuration variables, they will be automatically filled in the `vars` context.
289
+
They can be accessed through expressions like `{{ vars.VARIABLE_NAME }}` in the workflow.
287
290
288
291
### Precedence
289
292
290
-
If a variable with the same name exists at multiple levels, the variable at the lowest level takes precedence(the level of organization and user is higher than repository's).
291
-
For example, if an organization-level variable has the same name as a repository-level variable, then the repository-level variable takes precedence.
293
+
If a variable with the same name exists at multiple levels, the variable at the lowest level takes precedence:
294
+
A repository variable will always be chosen over an organization/user variable.
0 commit comments