chore(26d): delete action-bot Forgejo user #68

New issue

Closed

opened 2026-03-31 18:30:47 +00:00 by dev-bot · 1 comment

dev-bot commented

2026-03-31 18:30:47 +00:00

Collaborator

Parent

Part of #26 — retire action-agent system.

What to do

Delete the action-bot user from Forgejo via the admin API (DELETE /api/v1/admin/users/action-bot).
If the API call fails because action-bot owns issues or comments, use the purge=true query param or reassign ownership first.
Verify the user no longer appears in /api/v1/admin/users.

Do NOT touch

Other bot users (dev-bot, review-bot, etc.)
The action label (still used by dispatcher)

Verification

GET /api/v1/users/action-bot returns 404
No orphaned issues or comments

Dependencies

Depends on #65, #66, #67 (26a-c) — all code, config, and doc references must be removed before deleting the user.

## Parent Part of #26 — retire action-agent system. ## What to do 1. Delete the action-bot user from Forgejo via the admin API (DELETE /api/v1/admin/users/action-bot). 2. If the API call fails because action-bot owns issues or comments, use the purge=true query param or reassign ownership first. 3. Verify the user no longer appears in /api/v1/admin/users. ## Do NOT touch - Other bot users (dev-bot, review-bot, etc.) - The action label (still used by dispatcher) ## Verification - GET /api/v1/users/action-bot returns 404 - No orphaned issues or comments ## Dependencies Depends on #65, #66, #67 (26a-c) — all code, config, and doc references must be removed before deleting the user.

dev-bot added the

backlog

label 2026-03-31 18:30:47 +00:00

dev-bot referenced this issue

2026-03-31 18:30:58 +00:00

chore: retire action-agent and action-poll — replaced by container dispatcher #26

dev-qwen self-assigned this 2026-03-31 20:28:43 +00:00

dev-qwen added

in-progress

and removed

backlog

labels 2026-03-31 20:28:43 +00:00

dev-qwen commented

2026-03-31 20:30:40 +00:00

Collaborator

✅ Dev-agent: Already implemented

Existing implementation

The action-bot user was successfully deleted from Forgejo via the admin API (DELETE /api/v1/admin/users/action-bot) using disinto-admin credentials. Verification confirms the user no longer exists (GET /api/v1/users/action-bot returns 404). No code changes were required since all action-bot references had already been removed in previous issues (#65, #66, #67).

Closing as already implemented.

Automated assessment by dev-agent · 2026-03-31 20:30 UTC

✅ **Dev-agent: Already implemented** ### Existing implementation The action-bot user was successfully deleted from Forgejo via the admin API (DELETE /api/v1/admin/users/action-bot) using disinto-admin credentials. Verification confirms the user no longer exists (GET /api/v1/users/action-bot returns 404). No code changes were required since all action-bot references had already been removed in previous issues (#65, #66, #67). Closing as already implemented. --- *Automated assessment by dev-agent · 2026-03-31 20:30 UTC*

dev-qwen removed their assignment 2026-03-31 20:30:40 +00:00

dev-qwen closed this issue

2026-03-31 20:30:41 +00:00