Protect the renamed archetypes framework checkout #8
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/secrets!8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "agent/protect-archetypes-branch"
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?
Add a
work/allod/archetypes masterline togit/protected-branchesso the renamed framework checkout is guarded under its new name.The in-flight repo split renamed the framework repo
allod/profiles->allod/archetypes(already merged on the forge), and a new example-definitions repo now lives atallod/profiles. The existingwork/allod/profiles masterentry is kept unchanged because that path is now the new definitions repo and must stay protected. This is purely additive: one new line placed adjacent to the existing profiles entry.Refs allod/strategy#18
Risk
R1 Low. Additive guardrail-config line only. This file is the source of the agent git protected-branch guardrail: home-manager symlinks it to
~/.config/git/protected-branches, which the local pre-commit and pre-push hooks read to block direct commits and pushes to protected branches. The live~/.config/git/protected-branchesonly updates on the next VM home-manager rebuild, which is not part of this PR.Validation
nix flake checkpassed in the change worktree (checks: external-ssh-trust-targets, credential-inventory). The diff is exactly one added line,work/allod/archetypes master, adjacent to the existingwork/allod/profiles masterentry, with no other line changed.