docs: clarify Kanban board limitation and label-as-board workflow (#52)

This commit was merged in pull request #52.
This commit is contained in:
2026-07-15 22:04:28 +02:00
parent 4b4c05339e
commit 3d5550b07f
2 changed files with 36 additions and 0 deletions

View File

@@ -39,6 +39,11 @@ repository intentionally keeps its configuration inside `work_item/.work-item.ym
Do not change its repository identity, required tests, allow list, deny list, size
limit, or CI policy merely to bypass a workflow failure.
Story stage is tracked by `status/*` labels and issue open/close, which serve as the
board; `work-item` does not move cards between Gitea project-board columns (Gitea's API
cannot move cards). Use label-filtered issue views instead — see
`work_item/README.md` → "Kanban / project board position".
Workflow state is local at `.git/work-item-state.json` and must never be committed.
`claim` is resume-aware: