git/fetch: Unset core.hookspath for each repo during fetch

[credfeto]

As part of the fetch operation, unset core.hookspath for each repository if it is set, so that globally-configured hook paths don't persist on individual repos.

Prompt: as part of fetch, can you unset any git hooks directories if they're set on the repo

[dnyw4l3n13]

Implementation Plan

Files to change

• CHANGELOG.md — add a Fixed entry for unsetting core.hookspath in git/fetch during fetch (via dotnet changelog tool, not hand-edited)

Approach

The actual code change — git -C "$CURRENT_DIR" config --local --unset core.hookspath 2>/dev/null || true — was already added to git/fetch in commit c10775ef (4 Jun 2026) as part of a broader shell-script cleanup. No code change is needed. The only remaining work is:

1. Create a branch fix/617-fetch-unset-hookspath.
2. Add a Fixed entry to CHANGELOG.md using dotnet changelog -f CHANGELOG.md -a Fixed -m "git/fetch: Unset core.hookspath for each repo during fetch so that globally-configured hook paths do not persist on individual repos".
3. Commit, push, and open a draft PR that Closes #617.
4. Convert the PR to ready for review.

Test strategy

No automated tests exist for this shell script. Manual verification: after the CHANGELOG entry is merged, the issue will be closed. The underlying behaviour (hookspath being unset) is already exercised by anyone running git/fetch against repos with a global core.hookspath set.

Assumptions

• dotnet changelog is available in the environment (it is listed in the repo's dotnet tool manifest).
• No additional code change to git/fetch is needed — the fix is confirmed present on main.

Open questions

None — ready to proceed pending approval.

[credfeto]

Approved

[dnyw4l3n13]

Implemented: added a Fixed CHANGELOG entry for the core.hookspath unset behaviour in git/fetch, and opened PR #705 for review.