Question 1

How do I create Windows-safe filenames from ISO timestamps?

Accepted Answer

Replace colons with hyphens using a centralized utility like safeTimestamp(), which converts 2026-03-15T05:30:00Z to 2026-03-15T05-30-00Z. Colons are illegal in Windows filenames, so never inline .toISOString() directly into file paths.

Question 2

Why does git -C fail with Windows paths?

Accepted Answer

git -C is unreliable with Windows paths containing backslashes, spaces, or drive letters. Instead, change directory first with cd, then run git commands, and check git diff --cached --quiet before committing to avoid empty commits.

Question 3

How do I compare file paths on case-insensitive filesystems?

Accepted Answer

Check process.platform for win32 or darwin and lowercase both paths before comparing with startsWith. Linux filesystems are case-sensitive, so do not lowercase there. This matters for path traversal checks and rootDir confinement.

Question 4

Why do multi-line git commit messages fail in PowerShell?

Accepted Answer

Backtick-n newlines inside git commit -m fail silently in PowerShell. Write the message to a temp file with Set-Content and commit using git commit -F $msgFile, then remove the temp file.

Question 5

When should I not assume the current working directory is the repo root?

Accepted Answer

Never assume CWD is the repo root in cross-platform scripts. Use an explicit team root from the spawn prompt or run git rev-parse --show-toplevel, and build paths with path.join() or path.resolve() instead of string concatenation.

windows-compatibility

SYSTEM DOCUMENTATION & REQUIREMENTS

Frequently Asked Questions about windows-compatibility

Related Skills