feat: enforce issue-linked branches + versioning/tagging policy (#48) #49
Reference in New Issue
Block a user
Delete Branch "feat/issue-48-branch-release-standards"
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?
Closes #48. Refs #38, #39, #46.
Branch ↔ issue linkage (enforced)
scripts/worktree-startnow validates branch names:(fix|feat|docs|chore)/issue-<number>-<slug>review/pr-<number>-<slug>--allow-unlinkedoverrides;--dry-runpreserved.Claimed. Branch: … Worktree: …), andCloses #nvsRefs #nin PR bodies.Versioning / tagging policy (docs only)
vMAJOR.MINOR.PATCH(v0.x.ywhile unstable); PATCH/MINOR/MAJOR bump rules.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 remotemaster.skills/llm-project-workflow/templates/release-tag.md.Tests / checks
worktree-startvalidation tests: acceptsfix|feat|docs|chore/issue-123-…+review/pr-456-…; rejectsfix/random-name,my-branch, non-numeric issue; honors--allow-unlinked; preserves--dry-run. (Existing refuse-overwrite test updated to an issue-linked name.)bash -nclean;git diff --checkclean; secret scan of script/docs clean.Files changed
scripts/worktree-start,tests/test_worktrees.py,docs/llm-workflow-runbooks.md,skills/llm-project-workflow/SKILL.md,skills/llm-project-workflow/templates/release-tag.md(new).Process
Isolated worktree:
./scripts/worktree-start feat/issue-48-branch-release-standards→branches/feat-issue-48-branch-release-standards.⚠️ Authored by me — do not self-merge. Needs review by another author.
Pull request closed