Protect core Allod repos #4

Merged
vnprc merged 2 commits from agent/protect-core-repos into master 2026-07-14 18:25:40 +01:00
Member

Summary

Add allod/deploy, allod/nexus, allod/profiles, and allod/vm to the tracked protected-branches policy so future changes use agent branches and PRs instead of direct master commits.

Risk

Low. This only changes Git workflow policy data consumed by the existing Home Manager-managed hooks and allod change workflow. After merge, profiles must pick up the updated secrets input before managed homes see the new policy.

Validation

  • Verified git/protected-branches entries use the documented two-field format.
  • Confirmed via subagent inspection that allod change reads ~/.config/git/protected-branches and that the tracked source is allod/secrets/git/protected-branches.
  • Added the follow-up allod/deploy request as a second commit on the existing PR branch.
## Summary Add allod/deploy, allod/nexus, allod/profiles, and allod/vm to the tracked protected-branches policy so future changes use agent branches and PRs instead of direct master commits. ## Risk Low. This only changes Git workflow policy data consumed by the existing Home Manager-managed hooks and allod change workflow. After merge, profiles must pick up the updated secrets input before managed homes see the new policy. ## Validation - Verified git/protected-branches entries use the documented two-field format. - Confirmed via subagent inspection that allod change reads ~/.config/git/protected-branches and that the tracked source is allod/secrets/git/protected-branches. - Added the follow-up allod/deploy request as a second commit on the existing PR branch.
Author
Member

User requested adding allod/deploy to the protected branches policy in this PR.

User requested adding allod/deploy to the protected branches policy in this PR.
vnprc approved these changes 2026-07-14 18:25:34 +01:00
vnprc merged commit 606c8134fa into master 2026-07-14 18:25:40 +01:00
vnprc deleted branch agent/protect-core-repos 2026-07-14 18:25:40 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
allod/secrets!4
No description provided.