refactor
BREAKING
task/drop-issue-labels-junction
#1 / 1
refactor: drop dead musehub_issue_labels junction table
The musehub_issue_labels join table was built in anticipation of a normalized issue-label relationship that was never implemented. All service/API/template code reads and writes issue labels through musehub_issues.labels (ARRAY(text)) — the junction table was never inserted into and has always been empty.
Changes: - Remove MusehubIssueLabel ORM class and issue_labels relationship from MusehubLabel - Remove phantom DELETE FROM musehub_issue_labels cleanup from the label-delete route and MCP write tool (was cleaning an always-empty table) - Alembic 0026 drops the table and its index
Proposals continue to use musehub_proposal_labels correctly and are unaffected.
sha256:e33c113c1068372f5aefa0aafeff4cabc2d3db25cc4d226c67a688f38687ade2
sha
sha256:4882c9f32d693b2d590c14ec0f405abaecb82aa0ca7081914c3ca48d2a60214d
snapshot
← Older
Oldest on task/drop-issue-labels-junction
All commits
Newer →
Latest on task/drop-issue-labels-junction
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:e33c113c1068372f5aefa0aafeff4cabc2d3db25cc4d226c67a688f38687ade2 --body "your comment"
No comments yet. Be the first to start the discussion.