Skip to content

Mention the gh SSH Protocol Opt-In in the Host Setup READMEs #2644

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ptr727 merged 3 commits into from
Oct 9, 2026
Merged

Mention the gh SSH Protocol Opt-In in the Host Setup READMEs #2644

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2b09cad
Mention the gh SSH Protocol Opt-In in the Host Setup READMEs
ptr727 Oct 9, 2026
18f2e9a
Name the Configure Action and Split the Long Sentences in the gh Prot…
ptr727 Oct 9, 2026
778e860
Split the Remaining Long Sentences in the gh Protocol Mentions
ptr727 Oct 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions host-setup/linux/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,8 @@ Two steps cannot be automated, because they happen in a browser. The public key

**`--shared-checkout` exists because `safe.directory` and `core.sharedRepository` are relaxations, not defaults.** They are applied only for a path the caller names, and a host one account uses needs neither. `*` is accepted but called out as turning the ownership check off everywhere.

**`--gh-ssh-protocol` exists because rewriting a working authentication setup is the operator's call.** A plain run reports gh's github.com git protocol and `--configure` alone leaves it as found. `--configure --gh-ssh-protocol` sets it to ssh. It warns and sets nothing where gh is not installed or not logged in. A protocol set before a login leaves a tokenless entry that gh reports as a failed login.

## install-skills.sh Is the Exception

The sibling scripts are independently fetchable, and this one deliberately is not. It drives `scripts/skills_install.py` at the tree root, and the skills content lives in the tree, so a copy fetched alone has nothing to install. Python 3.7 or later is its one dependency, which is why the bootstrap runs it last. Run on a host without one, it stops and names the tools step as its prerequisite.
Expand Down
2 changes: 2 additions & 0 deletions host-setup/windows/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,8 @@ host-setup\windows\setup-github.ps1 -Status
host-setup\windows\setup-wsl.ps1 -Status
```

`setup-github.ps1` reports gh's github.com git protocol and `-Configure` alone leaves it as found, since rewriting a working authentication setup is the operator's call. `-Configure -GhSshProtocol` sets it to ssh. It warns and sets nothing where gh is not installed or not logged in. A protocol set before a login leaves a tokenless entry that gh reports as a failed login.

## Requirements

**PowerShell 7 or later**, which is `pwsh` rather than the `powershell.exe` that ships with Windows. Each script refuses an older one and prints `winget install --id Microsoft.PowerShell --exact --source winget` as the remedy. `pwsh` is deliberately not a managed tool: a host that cannot run these scripts cannot be repaired by them.
Expand Down
Loading