test: root-skip the update permission family; hermetic identity in initRepoAt #138
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!138
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "refs/pull/138/head"
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?
Summary
Completes the CI-under-root cleanup the first live Actions runs exposed. (1) All eight cmd/update permission-family tests (preflight refusal, permission-denied hints, sudo elevation/degradation, integrity-repair variants) use a 0o555 directory barrier that root walks through, so they failed in the root CI job container while passing on every dev machine - they now share a skipIfRoot helper with the rationale documented. (2) internal/mcp's initRepoAt fixture never set a committer identity, so the three foreign-dir tests that seed commits failed in CI where no global gitconfig exists - the fixture now sets repo-local user.name/user.email, matching the pattern every other git fixture in the repo already uses. Verified non-root locally (all three packages pass, tests execute) and as root inside the pinned CI image (update family skips, foreign-dir trio passes). Refs #47.