vole

Clone

Read only, no credentials:

https://rodent.software/vole.git

Write over SSH with a registered key:

git clone ssh://git@rodent.software: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/accounts-and-access.md +3−3

@@ -52,8 +52,8 @@ counts when it is not the author. Granting a role is the trust decision, and the
	52	52	audit log and every approval name the bot.
	53	53
	54	54	A workflow can act as a bot without holding a long-lived key. A job that names the
	55		account with `bot:` is given a credential when it is leased: a key generated for that
	56		run, written into the job, and gone when the run ends. The key may do what the
		55	account with `acts-as:` is given a credential when it is leased: a key generated for
		56	that run, written into the job, and gone when the run ends. The key may do what the
	57	57	account may do: discuss, file an issue, manage an item it wrote, open a change from a
	58	58	branch it may push, triage and approve when the role allows it, and push the branches
	59	59	the role allows. It cannot reach an admin surface, read repository secrets, or lease
@@ -62,7 +62,7 @@ work, because those are not repository writes.
	62	62	The credential is not the account's key, and it does not widen the role: a
	63	63	`contribute` bot's job still opens changes in its own namespace, and a job cannot
	64	64	approve unless its account can. See
	65		[Workflow reference § bot](reference/workflow-reference.md#bot). A bot may also hold an
		65	[Workflow reference § acts-as](reference/workflow-reference.md#acts-as). A bot may also hold an
	66	66	ordinary key, provisioned the way a person's is, for an automation that is not a
	67	67	workflow run. A CI runner is that case: the runner process uses the bot's ordinary
	68	68	key to lease work, while the jobs it runs still get a credential for the run. See