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/workflows.md +3−3

@@ -170,7 +170,7 @@ jobs:
	170	170	image-file: agent
	171	171	network: bridge
	172	172	timeout: 2h
	173		bot: coding-agent
		173	acts-as: coding-agent
	174	174	steps:
	175	175	- run: run-the-session
	176	176	```
@@ -188,13 +188,13 @@ not start it again. Mentions inside code samples are ignored. See
	188	188	for the exact rules.
	189	189
	190	190	The job acts as an account, so the account it uses should be a bot: it has no
	191		browser sign-in and is shown as a bot wherever its name appears. `bot:` names it, and
		191	browser sign-in and is shown as a bot wherever its name appears. `acts-as:` names it, and
	192	192	the instance gives the job a credential for that account when it is leased — one
	193	193	run's key, written into the job, gone when the run ends — so a comment or a change it
	194	194	writes is attributable and needs no long-lived key in a repository secret. The
	195	195	account's role still decides what it may do. See
	196	196	[Accounts and access § Bot accounts](accounts-and-access.md#bot-accounts) and
	197		[Workflow reference § bot](reference/workflow-reference.md#bot).
		197	[Workflow reference § acts-as](reference/workflow-reference.md#acts-as).
	198	198
	199	199	`network: bridge` is there because the session calls a model; `timeout` because a
	200	200	session can run longer than the ten-minute step default. A job that runs unattended