vole
Clone
Read only, no credentials:
https://rodent.software/git/vole.git
Write over SSH with a registered key:
git clone ssh://git@0.0.0.0:2222/vole.git
A free and open-source forge that lives in your Git repo.
Name the job's bot account with acts-as
ac541b268df7626894acdb3405a886a0f0d7cc4a · Keenan Nemetz · 6d ago · parent 57dc79af
Name the job's bot account with acts-as The field was `bot`, the same word as the account kind, so the YAML said "bot: coding-agent" and the reference page had to explain that the job acts as that account. The key now says what it does: `acts-as: coding-agent`. Nothing else moves. A bot is still a bot: `--bot`, the directory and profile badge, the kind column, and the accounts page all keep the word. The job model still calls the account Bot, because that is what it is. There is no alias. Unknown keys already fail the parse, the field has not shipped in a release, and this repository has no tags, so a second spelling would outlive the only reason to have one. A test pins the old key as rejected.
docs/reference/workflow-reference.md +4−4
| @@ -412,7 +412,7 @@ letter. At least one job is required. | |||
| 412 | 412 | | `runs-on` | string or list of strings | no | any runner | Runner labels the job requires. | | |
| 413 | 413 | | `network` | `none` or `bridge` | no | the runner's setting | Whether the job's container has a network. | | |
| 414 | 414 | | `secrets` | string or list of strings | no | none | Repository secrets the job reads, by name. Each name is also the variable a step finds it in. | | |
| 415 | | `bot` | account name | no | none | A bot account the job acts as, with a credential for that run. | | ||
| 415 | | `acts-as` | account name | no | none | A bot account the job acts as, with a credential for that run. | | ||
| 416 | 416 | | `env` | mapping | no | none | Environment every step of the job runs with. | | |
| 417 | 417 | | `timeout` | duration string | no | none | Wall clock the job's steps share. | | |
| 418 | 418 | | `steps` | list | yes | — | Commands the job runs. At least one is required. | | |
| @@ -647,7 +647,7 @@ best effort, and worth knowing exactly: | |||
| 647 | 647 | - an artifact, a site file or a release attachment is stored as the step wrote it, | |
| 648 | 648 | so a secret a step writes to a file it publishes is published. | |
| 649 | 649 | ||
| 650 | ### `bot` | ||
| 650 | ### `acts-as` | ||
| 651 | 651 | ||
| 652 | 652 | The bot account the job acts as: | |
| 653 | 653 | ||
| @@ -655,7 +655,7 @@ The bot account the job acts as: | |||
| 655 | 655 | jobs: | |
| 656 | 656 | triage: | |
| 657 | 657 | image-file: agent | |
| 658 | bot: coding-agent | ||
| 658 | acts-as: coding-agent | ||
| 659 | 659 | steps: | |
| 660 | 660 | - run: vole issue comment "$ISSUE" --reply-to "$COMMENT" -F reply.md | |
| 661 | 661 | ``` | |
| @@ -689,7 +689,7 @@ does not need to know it exists: | |||
| 689 | 689 | | `VOLE_KNOWN_HOSTS` | The known_hosts file with this instance's host key. | | |
| 690 | 690 | ||
| 691 | 691 | These four are set by the runner and cannot be replaced by the workflow's `env:`, | |
| 692 | the same rule as `CI` and `HOME`. A job that names no `bot` gets none of them and no | ||
| 692 | the same rule as `CI` and `HOME`. A job that names no `acts-as` gets none of them and no | ||
| 693 | 693 | credential, which is what every workflow had before this field existed. | |
| 694 | 694 | ||
| 695 | 695 | ### `timeout` | |