feat: enforce issue-linked branches + versioning/tagging policy (#48) #49
Closed
jcwalker3
wants to merge 1 commits from
feat/issue-48-branch-release-standards into master
pull from: feat/issue-48-branch-release-standards
merge into: :master
:master
:fix/issue-850-native-mcp-bootstrap
:fix/issue-860-dirty-orphan-worktree-recovery
:fix/issue-858-audit-merged-pr-aware
:docs/issue-656-mcp-restart-governance
:fix/issue-842-conflict-fix-lease-lifecycle
:feat/issue-628-autonomous-handoffs-orchestration
:fix/issue-790-slice-a-heartbeat-policy
:feat/issue-639-webui-system-health-dashboard
:feat/issue-637-timeline-model
:feat/issue-646-policy-guardrail-visibility
:feat/issue-638-webui-app-shell-phase1
:fix/issue-851-cleanup-worktree-before-remote-delete
:fix/issue-843-cross-role-allocation-handoff
:fix/issue-844-exclude-epic-containers
:feat/issue-634-readonly-system-health-api
:fix/issue-840-cross-role-queue-allocation
:feat/issue-822-atomic-install-authority-kernel
:feat/issue-633-console-authz-audit-model
:feat/issue-636-inventory-api
:fix/issue-815-preflight-worktree-forwarding
:feat/issue-812-publish-unpublished-commit
:feat/issue-635-project-registry-api
:feat/issue-798-worker-registry-schema
:feat/issue-610-live-remote-parity
:docs/issue-632-web-console-architecture
:fix/issue-760-exact-owner-renewal
:fix/issue-787-kill-segment-separators
:chore/issue-681-preserve-review-session-wip
1
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
8bff54d5ac |
feat: enforce issue-linked branches + document versioning/tagging policy (#48)
Formalize the branch↔issue relationship and add a release/version-tagging policy. Branch/issue linkage: - scripts/worktree-start now validates branch names: implementation branches must match (fix|feat|docs|chore)/issue-<number>-<slug>; review branches review/pr-<number>-<slug>. Untraceable names are rejected with a clear error (exit 2). New --allow-unlinked override for genuine exceptions. --dry-run preserved. - Documented issue → branch → worktree → PR → cleanup traceability in the runbook and the portable SKILL, including the claim-comment convention and Closes #n / Refs #n PR-body usage. - Noted that Gitea exposes no native issue→branch API field (only a PR head branch), so linkage is enforced via branch name + claim comment + PR body + cleanup. Versioning / tagging policy (docs only; no release automation yet): - SemVer vMAJOR.MINOR.PATCH (v0.x.y while unstable) with PATCH/MINOR/MAJOR bump rules. - Annotated tags only, from the exact commit on remote master, only after the full suite passes, with release notes referencing merged PRs/issues. Never tag feature branches, dirty worktrees, unreviewed/self-authored work, or commits not on remote master. - Release runbook in the runbook + SKILL, plus a new skills/llm-project-workflow/templates/release-tag.md prompt template. Tests: worktree-start branch validation — accepts fix/feat/docs/chore/issue-* and review/pr-*, rejects fix/random-name / my-branch / non-numeric issue, honors --allow-unlinked, preserves --dry-run. Full suite 291 passed / 0 failures; bash -n clean; git diff --check clean; no secrets. Release-tag automation (a scripts/release-tag helper) intentionally deferred to a later issue to keep this diff narrow and testable. Closes #48. Refs #38, #39, #46. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> |