feat(check): [scan] guarddog config flag — persistent opt-in (#105) → 1.29.0 - #112
Merged
Conversation
…local malware scan (#105) GuardDog was env-only (KIT_GUARDDOG=1). kit check now also honors `guarddog = true` under [scan] in .kit.toml (best-effort config read) so the opt-in is committed project config, not an ephemeral env var. Verified: config flag bypasses the opt-in skip. Skip message points at both. Foundation for a kit setup prompt. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
✅ Docker image built successfully
|
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
1 participant
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.
Addresses "how do I get the option to configure this in setup?" — GuardDog (#105) was enabled only via the ephemeral
KIT_GUARDDOG=1env var.kit checknow also honors a persistentguarddog = trueunder[scan]in.kit.toml(best-effort config read), so the opt-in is committed project config instead of a per-shell env var.scan.guarddog?: boolean(zod + interface;scanalready in KNOWN_SECTIONS).checkGuardDogenabled if envKIT_GUARDDOGor[scan].guarddog. Skip message points at both..kit.tomlwith[scan] guarddog = true(no env) bypasses the opt-in skip → reaches the lockfile check.Foundation for an interactive
kit setupprompt that writes the flag — left as a follow-up since safely mutating an existing.kit.toml(which may already have[scan.tooling]) needs a proper TOML-merge step, not a naive append.🤖 Generated with Claude Code