Adding .husky to SENSITIVE_PATHS breaks repos that commit .husky files but not the hook setup

[maxired]

Problem

PR #1174 added .husky to the SENSITIVE_PATHS list in src/github/operations/restore-config.ts. This causes the .husky directory to be restored/reset during the action, which breaks repositories that commit their .husky files but rely on npx husky being run to install the hooks.

After this change, pre-commit hooks no longer run because the hook setup is wiped and would need to be reinstalled via npx husky.

This is a regression from the previous behavior where .husky was not treated as a sensitive path.

Context

See the discussion on #1174: #1174 (comment)

Expected Behavior

Repositories that commit .husky directory contents should continue to have their git hooks work as expected after the action runs.

Suggested Fix

Either:

• Remove .husky from SENSITIVE_PATHS, or
• Only restore specific files within .husky that are security-sensitive (e.g., prevent the action from adding new hooks), rather than blanket-restoring the entire directory
• ask the model tu run npx husky or similar to re install correctly the hooks

[ashwin-ant]

@claude remove .husky from the list

[claude]

Claude finished @ashwin-ant's task in 53s —— View job • claude/issue-1203-20260410-0552 • Create PR ➔

---

Removing .husky from SENSITIVE_PATHS

• Read the source file and identify the change
• Remove .husky from SENSITIVE_PATHS
• Commit and push

Removed .husky from the SENSITIVE_PATHS list in src/github/operations/restore-config.ts. This fixes the regression from #1174 where repositories that commit their .husky directory would have their git hook setup broken by the action restoring/resetting the directory.

Note: I was unable to run bun test and bun run typecheck due to tool permissions — please verify CI passes on the PR.

|