windows-compatibility

Git automation on Windows often fails when using the `git -C` flag with local paths or embedding multiline commit messages in `-m`. Switching to a `cd`-first workflow and using a temp file with the `-F` flag resolves these cross-platform command invocation issues.

To format timestamps for filenames safely across Windows, macOS, and Linux, you must remove colon characters. Using a centralized safe timestamp format without colons prevents illegal character errors when generating cross-platform build artifacts.

The best way to handle file paths in CI automation scripts is to use `path.join()` or `path.resolve()` and derive the repo root reliably. Never assume the current working directory is the repo root to ensure operations run consistently across different operating systems.

Yes, PowerShell can break git commit messages with multiple lines due to newline handling pitfalls. To avoid this, write your commit message to a temporary file and pass it to git using the `-F` flag instead of the `-m` flag.

To make cross-platform build scripts run consistently on Windows runners, update your tooling to use safe timestamps without colons, avoid `git -C` by changing directories first, and resolve repo-relative paths using proper utilities like `path.join()`.

You should avoid using the `git -C` flag in CI pipelines when working with Windows paths to prevent unreliable behavior. Instead, use a `cd`-first workflow to change into the target directory before running your git operations.