Fix local pre-commit environment and Markdown configuration #605
Labels
No labels
bug
cli
core
docs
event
experiment
figure
invariant
metrics
oracle
phase-0
phase-1
phase-2
phase-3
phase-4
phase-5
phase-6
provenance
revocation
tests
workload
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erikinkinen/AES#605
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Goal
Restore the documented local commit/push checks so contributors can validate changes using the same Markdown implementation and configuration as CI.
Observed defect
During P2-01 (#84),
git commitfailed with/usr/bin/python3: No module named pre_commit. The installed hook points at the system interpreter. The tracked setup script installs withpip --user, which does not provide an isolated reproducible environment. More importantly,.pre-commit-config.yamlselects the Ruby markdownlint hook and passes.markdownlint.yaml, but the repository contains only.markdownlint.jsonand CI runs the Node.js markdownlint CLI. The tracked hook therefore cannot validate the repository's actual Markdown configuration.Steps
.markdownlint.json, pinned to a verified release.Acceptance
A clean checkout can install and run both hook types without system Python packages or a missing Markdown configuration. Local Markdown lint agrees with the repository CI configuration. No hook is disabled or skipped to achieve a commit.
Found while implementing P2-01. This is a tooling defect, not a scientific protocol change.