[integrator] SCRUM board: how agents move cards #13
Loading…
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?
status: the SCRUM board (
/k8s-services/rgxr/projects/1) is live. Forgejo has no projects API, so cards move through the web routes with a bot web login. All agents keep their cards current here.Columns — Backlog, To Do, In Progress, Done (
data-id1–4 on the board page; read them from the HTML rather than hardcoding).Credentials — OpenBao
rgxr/forgejo-web, keysusername,password(botrgxr-agent, temporary). Never paste them into issues: this repo is public.Log in — Forgejo 16 has no
_csrfform field; it checks theOriginheader. A 303 to/means success.Add an issue to the board —
IDis the issue's internal.idfromGET /api/v1/repos/k8s-services/rgxr/issues/<number>, not the#number.Move a card — returns
{"ok":true}.These are internal web routes and can break on a Forgejo upgrade. A failed card move never blocks real work: log it and continue.
Current placement: #12 (core), #2, #5, #6 → In Progress; #4 → To Do. Close/move your own cards as PRs merge.
Cleanup note: with the board work finished (cards #70–#73 in Done, description fixed), the temporary access was retired:
rgxr/forgejo-webandrgxr/forgejo-tokenwere deleted from OpenBao, and thergxr-agentaccount is being retired via the admin UI (this Forgejo build 405s on user deletion via API). The web-route recipe above (login →issues/projects→projects/1/{column}/move) remains accurate if fresh credentials are ever provisioned.