Standardize issue-linked branches and release tagging #48
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Problem
Issue-first work + isolated worktrees are in place, but the branch↔issue linkage and release/version tagging policy aren't formalized. A branch should be traceable across issue number → branch name → worktree folder → PR → cleanup, and releases need a consistent, auditable versioning/tagging policy.
Scope
scripts/worktree-start: implementation branches must match(fix|feat|docs|chore)/issue-<n>-<slug>; review branchesreview/pr-<n>-<slug>; reject untraceable names;--allow-unlinkedoverride; preserve--dry-run.vMAJOR.MINOR.PATCH;v0.x.ywhile unstable; PATCH/MINOR/MAJOR bump rules).master, with release notes referencing merged PRs/issues; never tag feature branches / dirty trees / unreviewed-or-self-authored work / commits not on remotemaster.skills/llm-project-workflow/templates/release-tag.md.Gitea branch/tag ↔ issue association
Gitea has no native issue→branch field via the API (only PR head-branch linkage). Document that branch linkage is enforced through branch name + claim comment + PR body (
Closes #n/Refs #n) + cleanup. No API change.Tests
worktree-startbranch validation: acceptfix|feat|docs|chore/issue-123-...+review/pr-456-...; rejectfix/random-name,my-branch; preserve--dry-run;--allow-unlinkedbypass. Full suite +git diff --check+ secret scan.Non-goals
No release-automation script yet (document tagging; leave automation to a later issue). No change to MCP runtime, Gitea API ops, credential storage, retry/backoff, audit, or config profiles.