gabriel / musehub public
feat patch dev-tools feat/186-bare-issue-ref-warning #1 / 1
AI Agent gabriel · 4 days ago · Sep 11, 2026 · Diff

feat(dev-tools): publish-issue.sh warns on bare #NNN cross-references (#186)

Discussed with gabriel: not worth automating stripping/replacement of staging-only ticket cross-references (#182, #183, etc.) — any meaningful auto-replacement either links back to staging (defeating the point) or needs nontrivial cross-referencing logic for a workflow that's already deliberately manual, low-frequency, and human-reviewed before every publish. A one-line warning does the actual job: it makes the human notice and decide (rewrite, remove, or leave as harmless context).

Matches the existing staging.musehub.ai URL warning pattern exactly — same shape, same non-blocking behavior. Regex requires digits immediately after '#' with no intervening whitespace, so markdown headings ("## Summary") never false-positive. 2 new tests (written first, confirmed red before the fix): bare references trigger the warning, markdown headings don't.

sha256:7c46d5416e26d73cc7a8353598caac8e0cfd13a60551dd7c9bfa081862d00823 sha
+3 ~2 symbols
2 changed · 1072 in snapshot files
sha256:0efb8c4ef4c9f668fd5ebb4222db3ef2aacb6934cd91b8578a9363b0e78a92de snapshot
+3
symbols added
~2
symbols modified
2
files changed
1072
files in snapshot
0
dead code introduced
Semantic Changes 5 symbols
~ scripts/dev/publish_issue.py .py 1 symbol added, 1 symbol modified
+ _BARE_ISSUE_REF_RE variable variable _BARE_ISSUE_REF_RE L34–34
~ tests/test_publish_issue.py .py 2 symbols added, 1 symbol modified
+ test_bare_issue_reference_in_body_triggers_warning method method test_bare_issue_reference_in_body_triggers_warning L120–129
+ test_markdown_heading_does_not_trigger_bare_reference_warning method method test_markdown_heading_does_not_trigger_bare_reference_warning L131–140
Files Changed
~2
1072 in snapshot
← Older Oldest on feat/186-bare-issue-ref-warning
All commits
Newer → Latest on feat/186-bare-issue-ref-warning

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:7c46d5416e26d73cc7a8353598caac8e0cfd13a60551dd7c9bfa081862d00823 --body "your comment"