Genericize private state-repo references in pm tooling and workspace docs #105
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/tools!105
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/fix-private-refs"
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?
Genericize hardcoded references to a private state repo in the public tools, so the PM tooling and workspace docs don't assume one operator's private checkout.
pm/pm: the header comment and the "state checkout not found" error hint namedvnprc/pm-statedirectly. The tool already resolves its state dir generically (ALLOD_PM_DIR, default$WORK_DIR/pm-state), so the messages now point at that path/override instead — a forker gets an actionable hint rather than an instruction to clone a repo they cannot access.workspace/README.md: replacedhashpool(an unrelated private project name) in the examplepull-all --switchoutput with a neutral placeholder.Out of scope by decision: the
vnprc/namespace elsewhere (for example thetests/git-hooks/protected-refs-policy.shfixture) is left as-is — the maintainer's nym is already public in the commit history and is not treated as sensitive. This PR only removes the portability-breaking hardcode and the unrelated private project name.Risk
Text-only edits (one comment, one error string, one docs example); no code paths change.
Validation
pmresolves its state dir viaALLOD_PM_DIR/$WORK_DIR/pm-stateexactly as before — only the two message strings changed. Confirmed no remainingvnprc/pm-stateorhashpoolin the tool or workspace docs.3a305f651bto88b9dccb89