Include linked hook documentation in the image build stage #59
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/Documentation!59
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/documentation-build-readme"
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?
Image run 342 attempt 1 passed the source scan, then failed npm run check:links because README.md links to .githooks/README.md and that file was missing from the image build stage. Copy only that document before validation and record the run outcome.
Validation: reproduced the exact failure using only the Dockerfile COPY inputs, then confirmed the same link checker passes after adding the document. npm run check, git diff --check and native Gitleaks 8.30.1 staged/default-rule scanning passed. Published blobs match the validated files; author and committer are kiyi kiyi@gitchegumi.com. Full local npm run build remains blocked by the existing Turbopack CSS subprocess failure. No local Docker build was attempted.
A fresh approved owning image build is still required after merge and passing checks. No manual workflow or deployment was dispatched. Tracks #56.
Failed run: https://git.gitchegumi.com/Homelab/Documentation/actions/runs/342/jobs/1/attempt/1
Reviewed exact head
8de6cf601d: the build stage now copies only.githooks/README.mdbeforenpm run check:links, addressing the missing target linked from the root README without copying the hook executables into the image. The operations note correctly distinguishes run 342's source-scan success and link-check failure from image publication or deployed rendering, and requires a fresh approved image build after merge. This change does not alter UDS packaging, admission, policy, gateway, or routing ownership. No source blocker found. I did not independently execute a Docker build or verify the claimed local checks. Source security and documentation checks are still pending at this head; their success is a separate merge gate, not established by this approval.CI at submission: pending. This is a source-review approval, not a scan verdict; required checks still block merge.