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/runner.md +1−1

@@ -61,7 +61,7 @@ clone without giving the machine write access.
	61	61
	62	62	The `--key` is long-lived: it authenticates the runner process for as long as the
	63	63	account is active. It is not the credential a job uses. A workflow job that names
	64		a bot with `bot:` still gets a key minted for that run, scoped to the repository
		64	a bot with `acts-as:` still gets a key minted for that run, scoped to the repository
	65	65	and the run, and gone when the run ends; that key cannot lease work. Keep one key
	66	66	per runner machine, readable only by the runner user, so a host you stop trusting
	67	67	is revoked by removing that key or retiring the account.