Repository navigation
Wire the shared commit guards into this repo (owner merges — this push publishes) - #28
Merged
Merged
Conversation
…zed blob or a stray secret here Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This repo has no commit-time guard chain, so nothing here refuses an oversized blob (GitHub hard-rejects anything over 100 MiB, and by then it is already in history and costs a rewrite), a stray credential, or a subagent-memory file that belongs in
pablo-tech/plover-context..githooks/pre-commitis the thin shim every already-wired repo carries, byte-identical. The guard logic stays inplover-context(infra/git-hooks/guards.sh), so a threshold or a new guard changes in one place and never here; each guard scopes itself, so the ones that do not apply to this repo exit 0.core.hooksPathis local config and does not travel with a clone. On every machine holding this repo, after merging:Found by
plover-context'sscripts/doctor.shonce its coverage was derived frominfra/standards/estate.jsoninstead of a hardcoded list of six paths (pablo-tech/plover-context#282) — this repo was one of six committing unguarded.Left open deliberately: merging this publishes. Every push to
mainhere bumps the patch and runsnpm publishfor @tinytars/vault, and npm does not take a version back. The job keys on the push, not on the paths, so a.githooks-only diff is not an exemption — a.githooks-only merge cut@promontory-studio/dokimasia0.3.3 on 2026-09-25. Merge whenever a release is acceptable; nothing else waits on it.This repo also has no
devbranch, so there is nowhere else to land it.🤖 Generated with Claude Code