Skip to content

Release v1.3.1: read git.allowTrunkPush through a relative hooks path - #19

Merged
RobHofmann merged 2 commits into
mainfrom
18-relative-hooks-path
Nov 9, 2026
Merged

RobHofmann merged 2 commits into
mainfrom
18-relative-hooks-path

Conversation

@RobHofmann

Copy link
Copy Markdown
Owner

Refs #18

What changes

  • The pre-push git hook resolves the config module path before Import-Module. core.hooksPath is relative, so the path was relative too, and Import-Module read it as a module name. The setting then counted as off, and every push to main was refused.
  • A new test runs a real git push through a relative core.hooksPath, with the setting on and off. It fails on the v1.3.0 hook.
  • On main or master with git.allowTrunkPush on, the pre-flight issue-contract row is SKIP instead of FAIL. It stays FAIL on any other branch without a story key.
  • layout.md names the SKIP row. The CHANGELOG has a v1.3.1 entry, and every package is at 1.3.1.

Checks

The pre-flight passes: gates, tests and the secret scan.

…ssue row on main

The pre-push hook passed a relative module path to Import-Module, which
read it as a module name, so every push to main was refused. On main with
the setting on, the pre-flight issue-contract row is now SKIP.

Refs #18
@RobHofmann
RobHofmann merged commit fb90610 into main Nov 9, 2026
16 checks passed
@RobHofmann
RobHofmann deleted the 18-relative-hooks-path branch November 9, 2026 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant