domverse/photoanalyzer
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

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

Merged
domverse merged 1 commits from docs/kanban-board-limitation into main 2026-07-15 22:04:29 +02:00
Conversation 0 Commits 1 Files Changed 2 +36
domverse commented 2026-07-15 22:04:16 +02:00
Owner
Copy Link

work-item drives story stage via status/* labels + issue open/close, which are the board. It cannot move Gitea project-board columns: Gitea's REST API has no project endpoints and card moves require a logged-in web session (an API token only authenticates /api/*). Documents the recommended label-filtered views and the limitation.

work-item drives story stage via status/* labels + issue open/close, which are the board. It cannot move Gitea project-board columns: Gitea's REST API has no project endpoints and card moves require a logged-in web session (an API token only authenticates /api/*). Documents the recommended label-filtered views and the limitation.
domverse added 1 commit 2026-07-15 22:04:17 +02:00
docs: explain why work-item cannot move Gitea board cards ff8260536f 
work-item tracks story stage via status/* labels and issue open/close (the
board), not Gitea project-board columns. Gitea's REST API exposes no project
endpoints and its web move-endpoints need a logged-in session; an API token
only authenticates /api/*. Document the label-as-board approach and the
limitation in the README and AGENTS.md.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
domverse merged commit 3d5550b07f into main 2026-07-15 22:04:29 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
area/backend
Backend services, jobs, or API
 area/database
Schema, persistence, migration, or queries
 area/filesystem
Filesystem identity, mutation, or storage
 area/frontend
Browser UI and client-side application
 area/integration
External tools or provider integrations
 area/testing
Automated test suites, fixtures, and tooling
 priority/critical
Release-blocking safety or correctness
 priority/high
Important phase outcome
 priority/normal
Normal planned work
 status/backlog
Awaiting dependency eligibility or prioritization
 status/blocked
Cannot proceed without an explicit resolution
 status/done
Merged, tested, and completed
 status/in-progress
Currently being implemented
 status/ready
Eligible to be claimed
 status/review
Submitted in a pull request for review
 type/feature
User-facing or domain capability
 type/hardening
Security, resilience, operations, or release hardening
 type/migration
Donor extraction, migration, or legacy consolidation
 type/test
Automated test infrastructure or acceptance coverage
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
domverse
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: domverse/photoanalyzer#52
Delete Branch "docs/kanban-board-limitation"

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?