Defame1297/holocron
0
0
Fork 0
Code Issues 14 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

feat: tests/test-pre-commit-installed.sh #55

New Issue
Closed
opened 2026-06-28 19:27:03 +00:00 by Claude · 1 comment
Claude commented 2026-06-28 19:27:03 +00:00
Collaborator
Copy Link

Scope

Write tests/test-pre-commit-installed.sh — verifies:

  • .pre-commit-config.yaml is present
  • Pre-commit framework is installed
  • Hooks run successfully on a dry run
## Scope Write `tests/test-pre-commit-installed.sh` — verifies: - `.pre-commit-config.yaml` is present - Pre-commit framework is installed - Hooks run successfully on a dry run
Claude added this to the Tooling milestone 2026-06-28 19:27:03 +00:00
Claude added the Kind/Feature
Priority
Medium
3
 labels 2026-06-28 19:27:03 +00:00
Claude commented 2026-09-09 18:52:15 +00:00
Author
Collaborator
Copy Link

Closing without action — reviewed during grill-with-docs triage of the small-issue batch. Pre-commit installation and successful hook execution are already exercised incidentally across the existing hook-related test suites (e.g. test-vale-hooks-consumer.sh, test-git-hooks-install.sh), README.md's Prerequisites table already documents pre-commit as a required pre-push dependency, and tests/run-tests.sh --strict already turns a missing pre-commit binary into a hard failure via the exit-77 skip convention. A dedicated test-pre-commit-installed.sh would duplicate that coverage without adding a new failure mode it doesn't already catch. Reopen if a gap is found that the existing suites don't actually cover.

Closing without action — reviewed during grill-with-docs triage of the small-issue batch. Pre-commit installation and successful hook execution are already exercised incidentally across the existing hook-related test suites (e.g. test-vale-hooks-consumer.sh, test-git-hooks-install.sh), README.md's Prerequisites table already documents pre-commit as a required pre-push dependency, and tests/run-tests.sh --strict already turns a missing pre-commit binary into a hard failure via the exit-77 skip convention. A dedicated test-pre-commit-installed.sh would duplicate that coverage without adding a new failure mode it doesn't already catch. Reopen if a gap is found that the existing suites don't actually cover.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Kind/Feature
Priority
Medium
3
Milestone
No items
No Milestone Tooling
Projects
Clear projects
No project
Assignees
Clear assignees
Claude renovate-bot Defame1297
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Defame1297/holocron#55
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?