project-manager/src/project_manager/project/cli/ at master · snowytrees.dev/project-manager · Tangled

snowytrees.dev / project-manager

0

Integrated repository, worktree, git stacker, and project manager

0

project-manager / src / project_manager / project / cli /

at master 1 folder 6 files

Jordan Isaacs project status: exit 0 regardless of worktree health 4w ago

rename core project create/delete modules to add/remove Follow-up to the wt add/remove CLI rename: the core ops are worktree addition/removal (container lifecycle is a side effect), so name them that way. project/create.py -> add.py (add, AddedWt, ADDED_COLUMNS), project/delete.py -> remove.py (remove, plan_remove, RemovePlan), emit_delete_plan -> emit_remove_plan. Also fixes the stale attach|detach|delete reference in the generated project README template. CLI command names are untouched.

1 month ago

project status: exit 0 regardless of worktree health `pm project status` is a report, not a health gate — it should fail only on an actual error (unknown project, IO), not because a worktree is non-ACTIVE. The old `return 1 if any non-ACTIVE worktree` treated intentional DETACHED worktrees (and informational DRIFT / mid-op OPS_OWNED) as failures, which made the Emacs status/stacker buffers refuse to render valid output. Always return 0 on success; genuine errors still raise and exit non-zero via the central CLI handler. `pm check` remains the linter-style gate whose exit code tracks health.

1 month ago

_plan_printers.py

rename core project create/delete modules to add/remove Follow-up to the wt add/remove CLI rename: the core ops are worktree addition/removal (container lifecycle is a side effect), so name them that way. project/create.py -> add.py (add, AddedWt, ADDED_COLUMNS), project/delete.py -> remove.py (remove, plan_remove, RemovePlan), emit_delete_plan -> emit_remove_plan. Also fixes the stale attach|detach|delete reference in the generated project README template. CLI command names are untouched.

1 month ago

rename core project create/delete modules to add/remove Follow-up to the wt add/remove CLI rename: the core ops are worktree addition/removal (container lifecycle is a side effect), so name them that way. project/create.py -> add.py (add, AddedWt, ADDED_COLUMNS), project/delete.py -> remove.py (remove, plan_remove, RemovePlan), emit_delete_plan -> emit_remove_plan. Also fixes the stale attach|detach|delete reference in the generated project README template. CLI command names are untouched.

1 month ago

rename core project create/delete modules to add/remove Follow-up to the wt add/remove CLI rename: the core ops are worktree addition/removal (container lifecycle is a side effect), so name them that way. project/create.py -> add.py (add, AddedWt, ADDED_COLUMNS), project/delete.py -> remove.py (remove, plan_remove, RemovePlan), emit_delete_plan -> emit_remove_plan. Also fixes the stale attach|detach|delete reference in the generated project README template. CLI command names are untouched.

1 month ago

style: ruff format pass over src/ and tests/ Mechanical run of `uv run ruff format src tests`. No behavior change — just line wrapping and trailing-comma normalization that the project hadn't been applying. Listed in `.git-blame-ignore-revs` (added next commit) so `git blame` skips this revision.

2 months ago

project status: exit 0 regardless of worktree health `pm project status` is a report, not a health gate — it should fail only on an actual error (unknown project, IO), not because a worktree is non-ACTIVE. The old `return 1 if any non-ACTIVE worktree` treated intentional DETACHED worktrees (and informational DRIFT / mid-op OPS_OWNED) as failures, which made the Emacs status/stacker buffers refuse to render valid output. Always return 0 on success; genuine errors still raise and exit non-zero via the central CLI handler. `pm check` remains the linter-style gate whose exit code tracks health.

1 month ago