Closes #173.
What changes
A job names the account it acts as with acts-as::
jobs:
triage:
image-file: agent
acts-as: coding-agent
steps:
- run: vole issue comment "$ISSUE" --reply-to "$COMMENT" -F reply.md
bot stays the word for the account itself: --bot, the directory and profile
badge, the kind column, and the accounts page all keep it. Only the job field
moves, because that is the place where “bot” was standing in for a verb.
Why
The field said what the value is, not what the job does with it. bot: next to
image-file: and runs-on: reads like another kind of setting, and the reference
page had to explain in prose that the job acts as that account. acts-as: says it
where the name is written. It also stops the one word meaning two things in the
same file, where the field bot took a value that is also called a bot.
What stays the same
- The parsed job still calls the account
Bot, and the run record still stores it in the same column, so the run page keeps saying which account acted. - The account still has to be a bot, active, and allowed to act in the repository; that check still happens when the job is leased, not at push.
- A bad name is still refused at push, now as
jobs.<id>.acts-as: ....
Old spelling is not accepted
bot: is an unknown key, so a workflow that still uses it fails the parse with the
file named. There is no alias on purpose: the field has not shipped in a release and
this repository has no tags, so this is the only window where one name is free, and
a permanent second spelling would outlive the reason for it. A test pins the old key
as rejected, so an alias cannot come back by accident.
Anyone with a local workflow file from main needs to change one line.
Checks
vole workflow run verify— passed locally (format, vet, build, licenses, links, packaging, race tests).vole workflow check—ok: 2 workflow(s).