git-version-controllisted

# Git Version Control ## Overview Create a repeatable git-based versioning workflow for experiments and code changes. Record each version with both git artifacts (commit/tag) and human-readable differentiators in a version log. ## Workflow 1. Inspect repository state before versioning. 2. Define version scope and naming. 3. Create commit and optional tag. 4. Update version log with characteristics and distinguishing points. 5. Validate traceability (`git show`, `git log`, file references). ## Step 1: Inspect State Run: - `git status --short` - `git branch --show-current` - `git log --oneline -n 5` If working tree contains unrelated dirty files, avoid touching them. Never use destructive reset/checkout unless user explicitly requests. ## Step 2: Define Version Identity Prefer one clear version token: - `v<major>.<minor>.<patch>` for stable releases - `<topic>_YYYYMMDD_HHMM` for experiment snapshots Recommended commit title format: - `<scope>: <version-token> <short-change-intent>` - Example: `delay-model: v0.3.1 enable criticality feed in scorer` ## Step 3: Commit and Tag Typical sequence: ```bash git add <changed-files> git commit -m "<scope>: <version-token> <short-change-intent>" git tag -a "<version-token>" -m "<summary>" # optional but recommended for checkpoints ``` If user wants comparison-only checkpoint without tagging, skip tag and record commit hash in log. ## Step 4: Record Version Characteristics and Distinguishing Points Maintain one log file for