Skip to content

fix(antigravity): use forward slashes in hooks.json commands (#466) - #494

Open
ZacLou wants to merge 1 commit into
monk-io:mainfrom
ZacLou:fix-hooks-json-backslashes-466
Open

ZacLou wants to merge 1 commit into
monk-io:mainfrom
ZacLou:fix-hooks-json-backslashes-466

Conversation

@ZacLou

@ZacLou ZacLou commented Sep 5, 2026

Copy link
Copy Markdown

Closes #466

Replaces Windows backslashes with forward slashes in .antigravity-plugin/hooks.json command strings so POSIX /bin/sh no longer consumes them as escape characters. The scripts/run-powershell.cmd shim already exits 0 when run under sh, and the sibling .sh hook entry performs the real work on Linux/macOS.

  • Adds a regression test.

@ZacLou
ZacLou force-pushed the fix-hooks-json-backslashes-466 branch from 2e87336 to 8070064 Compare September 16, 2026 10:03
…#466)

Replaces Windows backslashes with forward slashes in .antigravity-plugin/hooks.json command strings. The run-powershell.cmd shim already has a POSIX guard that exits 0 on sh, so the .cmd entry is safe to run on Linux/macOS when invoked with forward slashes, while the sibling .sh entry does the real work.

Adds a regression test.
@ZacLou
ZacLou force-pushed the fix-hooks-json-backslashes-466 branch from 8070064 to b9f55ea Compare September 16, 2026 20:25
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.

[Bug bounty] Cross-platform hook execution fails on Linux/POSIX due to unescaped Windows backslashes in hooks. json

1 participant