From f1dd2a67b9c9006f8e190af83b88b982b800620a Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Thu, 3 Sep 2026 23:05:08 +0000 Subject: [PATCH] Fix broken /script link in CONTRIBUTING.md (#63072) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 8650fe68-93b8-410f-9550-724098bbf954 --- .github/CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 4b2241b81c84..5719e174063d 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -116,7 +116,7 @@ This site can be developed on Windows, however a few potential gotchas need to b 1. Regular Expressions: Windows uses `\r\n` for line endings, while Unix-based systems use `\n`. Therefore, when working on Regular Expressions, use `\r?\n` instead of `\n` in order to support both environments. The Node.js [`os.EOL`](https://nodejs.org/api/os.html#os_os_eol) property can be used to get an OS-specific end-of-line marker. 2. Paths: Windows systems use `\` for the path separator, which would be returned by `path.join` and others. You could use `path.posix`, `path.posix.join` etc and the [slash](https://ghub.io/slash) module, if you need forward slashes - like for constructing URLs - or ensure your code works with either. -3. Bash: Not every Windows developer has a terminal that fully supports Bash, so it's generally preferred to write [scripts](/script) in JavaScript instead of Bash. +3. Bash: Not every Windows developer has a terminal that fully supports Bash, so it's generally preferred to write new scripts in TypeScript rather than Bash. 4. Filename too long error: There is a 260 character limit for a filename when Git is compiled with `msys`. While the suggestions below are not guaranteed to work and could cause other issues, a few workarounds include: - Update Git configuration: `git config --system core.longpaths true` - Consider using a different Git client on Windows