windows-compatibility

Prevent cross-platform git workflow errors by changing directories before running git commands, checking staged changes with git diff --cached --quiet, and writing commit messages to a temporary file used with git commit -F to avoid PowerShell pitfalls.

ISO timestamps cause illegal filename errors on Windows because colons are invalid characters in NTFS filenames. Sanitize ISO timestamps by replacing colons with hyphens using a safeTimestamp() utility to ensure cross-platform path compatibility.

Handle file paths reliably across Windows, macOS, and Linux by using path.join() or path.resolve() utilities for path construction instead of manual separator concatenation, which prevents failures caused by OS-specific path separators.

Using git -C can cause silent failures on Windows file paths due to shell behavior differences. Avoid git -C by changing directories explicitly first, then running git commands to ensure reliable cross-platform execution.

Standardize timestamps and paths for CI pipelines by centralizing timestamp formatting to replace colons with hyphens and using path utilities for construction, preventing illegal filenames and path errors across Windows, macOS, and Linux.

Check for staged changes before running git commit in cross-platform scripts by using the git diff --cached --quiet command, which prevents empty commits and avoids shell-specific syntax issues across Windows, macOS, and Linux.