repo_shape.py and the tools that print paste lines: under Git Bash (MSYSTEM set) the host-quoted lines are quoted for sh, not PowerShell, so a pasted NEXT line works in the shell that printed it (#532, option (a)) #711

Goal: every line a tool prints for a person to paste works in the shell they ran the tool from, Git Bash included.

Filed by lane openRepoShape-5 on Brett Heap's word of 2026-10-16T13:07:34Z, "take all recommendations". It chose option (a) of the Git Bash quoting question that #532 left open: use sh quoting under Git Bash, keyed on MSYSTEM, after #630.

• It is in milestone v1.1.1, under his "yes create v1.1.1" of 13:35:28Z, because it is a follow-up and not a regression.
• The other options were (b), keep os.name and tell Git Bash readers to paste into PowerShell, and (c), make the tools POSIX-only.

Sources:

• Tracking: setup, scaffold, family and the shared helpers, creating projects and families #459, comment 6204717473: "In Git Bash the host-quoted lines are still quoted for PowerShell. This extends L2-29, which names setup's family lines through shell_word alone."
• tests: a tests-git-bash job runs the launcher's and install.sh's suites in Git for Windows' own bash, so README and the handbook say Git Bash runs the one-line install, tested in CI but for a typed yes, which it cannot take there (#585) #596's writer's checklist candidate 7 (Git Bash on Windows: run the launcher and install.sh tests under Git Bash in the Windows job, so the one-line install is tested there (follow-up to #564) #585).

Lines

• The host dialect is os.name alone.
  • scripts/repo_shape.py's shell_quoted and shell_line quote for PowerShell whenever os.name == "nt", so a line printed under Git Bash is quoted for a shell the person is not in.
  • Direction: one host-dialect question in scripts/repo_shape.py. A Windows host whose environment has MSYSTEM set (Git Bash or MSYS2) is POSIX for printed lines, and every other Windows host keeps PowerShell quoting.
  • Every caller of the host dialect uses it: tests/test_readme_windows_quoting_sentence.py's inventory names those tools.
• L2-29: setup's family lines go through shell_word alone. Bring them under the same question.
• The docs say which shell the lines are for.
  • README's Windows quoting sentence (README.md, about :152-158 at main) and the handbook's Windows panel say the lines are for PowerShell.
  • Once this lands they should say that Git Bash gets sh quoting. Lane 3's README, AGENTS.md, docs/cli.md and the handbook: pipx install openreposhape is the second way in and the first on native Windows, git-filter-repo is installed in install.sh's order and never with a bare pip install, and a first draft of the v1.1.0 release notes (#563) #630 rewrites that panel, so land after it.

Tests: emulate MSYSTEM on Linux, with os.name patched as the existing quoting tests do. CI's tests-git-bash job (windows-latest) then runs the launcher and installer suites under a real Git Bash.

Pinned copies: scripts/repo_shape.py is copied into every project, so this is a re-pin, and it rides in v1.1.1's shape bump.

Overlaps: lane 3's #630 (the README and the handbook), and lane 5's #665 (the quoting-sentence inventory's gaps; it changes no quoting).

Mark each line → this issue on #459, and tick it there when this closes.

🤖 Generated with Claude Code