Skip to content

refactor: name automation templates after the action, not the agent - #531

Merged
VascoSch92 merged 1 commit into
mainfrom
vasco/rename-agent-automation-templates
Sep 3, 2026
Merged

refactor: name automation templates after the action, not the agent#531
VascoSch92 merged 1 commit into
mainfrom
vasco/rename-agent-automation-templates

Conversation

@VascoSch92

@VascoSch92 VascoSch92 commented Sep 3, 2026

Copy link
Copy Markdown
Member
  • A human has tested these changes.

Why

Three automation catalog entries are named after an agent rather than after the work they do, so the template card tells a user who is acting instead of what will happen. They are also the only Title Case names in a catalog that is otherwise sentence case.

Summary

  • Renamed three catalog entries so the name is the action: GitHub Issue to PR AgentGitHub issue to PR, GitHub Code Review AgentGitHub code review, QA Changes AgentQA changes.
  • Updated the worked example in automations/README.md, which quotes the github-pr-reviewer entry.
  • Updated tests/fixtures/automations/github-pr-reviewer.json, because a created automation's name is derived from the entry name (_derive_name in tests/test_automation_setup.py) and that test compares the derived request body to these fixtures byte for byte.

AGENTS.md Maintainer is left alone: that is the name of a file, not an agent mention. The QA Agent section header that the qa-changes automation writes into a PR description is also untouched, since the automation's filter expression depends on that exact string.

Issue Number

Fixes #532

How to Test

uv run --group test pytest

785 passed, 8 skipped locally with the live integration smoke deselected. tests/test_automation_setup.py and tests/test_catalog_schema.py cover the renamed entries and the updated fixtures.

Video/Screenshots

Not applicable, this is a copy change in the catalog manifests.

Notes

Agent Canvas pins @openhands/extensions, so the new names reach users on the next version bump.

Three catalog entries were named after an agent rather than the work they
do. Drop the Agent suffix and match the sentence-case naming the rest of
the catalog already uses.

- GitHub Issue to PR Agent -> GitHub issue to PR
- GitHub Code Review Agent -> GitHub code review
- QA Changes Agent -> QA changes

The created automation's name is derived from the entry name, so the
github-pr-reviewer request fixtures move with it.
@github-actions github-actions Bot added the type: refactor Code refactoring label Sep 3, 2026
@VascoSch92
VascoSch92 merged commit aa3fe65 into main Sep 3, 2026
13 of 14 checks passed
@VascoSch92
VascoSch92 deleted the vasco/rename-agent-automation-templates branch September 3, 2026 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type: refactor Code refactoring

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Name automation templates after the action, not the agent

3 participants