chore: drop goneat guardian from git hooks - #3
Merged
Merged
Conversation
Regenerate and install pre-commit/pre-push without --with-guardian. Remove leftover guardian comment residue from generated hook scripts. Co-Authored-By: Grok Code (fast) <grok@x.ai> Role: devlead Supervised-By: @3leapsdave
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.
Summary
pre-commit/pre-pushhooks without--with-guardian.goneat/hooks.yamlwas already guardian-free (assess-only)Why
Guardian approval on push blocked release tag pushes in the agent harness. Assessment gates remain.
Test plan
goneat hooks generate(no--with-guardian)# Guardian enforcement…commentsgoneat hooks installguardianstrings in.goneat/hooks/or installed.git/hooks/{pre-commit,pre-push}After merge: delete
v0.1.6tag (local+remote) and re-run post-merge tag/sign/upload on the new tip.