2 Commits

Author	SHA1	Message	Date
Qiiks	f5a95203a4	fix(shell-env): check SHELL before PSModulePath for shell detection ... On Windows, PSModulePath is always set by the system even when the active shell is Git Bash (via SHELL env var). This caused the non-interactive-env hook to generate PowerShell syntax ($env:VAR=val) for bash shells, resulting in 15+ errors per command. The fix prioritizes SHELL over PSModulePath since an explicit SHELL variable indicates the user's chosen shell, while PSModulePath is just a system-wide module path that doesn't indicate the active shell. Fixes: #3338	2026-04-11 16:06:42 +05:30
Sisyphus	d6499cbe31	fix(non-interactive-env): add Windows/PowerShell support (#573) ... * fix(non-interactive-env): add Windows/PowerShell support - Create shared shell-env utility with cross-platform shell detection - Detect shell type via PSModulePath, SHELL env vars, platform fallback - Support Unix (export), PowerShell ($env:), and cmd.exe (set) syntax - Add 41 comprehensive unit tests for shell-env utilities - Add 5 cross-platform integration tests for hook behavior - All 696 tests pass, type checking passes, build succeeds Closes #566 * fix: address review feedback - add isNonInteractive check and cmd.exe % escaping - Add isNonInteractive() check to only apply env vars in CI/non-interactive contexts (Issue #566) - Fix cmd.exe percent sign escaping to prevent environment variable expansion - Update test expectations for correct % escaping behavior Resolves feedback from @greptile-apps and @cubic-dev-ai --------- Co-authored-by: sisyphus-dev-ai <sisyphus-dev-ai@users.noreply.github.com>	2026-01-15 16:04:06 +09:00