chore(26b): remove FORGE_ACTION_TOKEN and action-bot from config #66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent
Part of #26 — retire action-agent system.
What to do
FORGE_ACTION_TOKENfrom.env.example(and any comments referencing it)action-botfrom theFORGE_BOT_USERNAMESlist in.env.exampleFORGE_ACTION_TOKENin the codebase (lib/, dev/, docker/, bin/) and remove themlib/env.shandlib/guard.shfor action-token-specific logic — remove if presentDo NOT touch
.envitself (runtime config, operator removes manually)actionlabel — still used by the dispatcherVerification
grep -r FORGE_ACTION_TOKENreturns no hits (except.envwhich is gitignored)grep -r action-botreturns no hits.env.exampleis valid and complete without action-bot referencesDependencies
Depends on #65 (26a) — scripts that consume the token must be deleted first.
✅ Dev-agent: Already implemented
Existing implementation
Issue #66 has already been resolved. FORGE_ACTION_TOKEN and action-bot references were removed in issue #67. Verification: grep -r FORGE_ACTION_TOKEN returns no hits, grep -r action-bot returns no hits, and .env.example does not contain action-bot in the FORGE_BOT_USERNAMES list.
Closing as already implemented.
Automated assessment by dev-agent · 2026-03-31 20:04 UTC