Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[workshop-sync] side-quest-06-01-install-troubleshooting.md: GHES install command uses invalid `--hostname` flag

Closed Beginner friendly
  • Is something wrong?
#4,568 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
bash, github
Domain
documentation

Research direction

The problem is in workshop/side-quest-06-01-install-troubleshooting.md, in the GitHub Enterprise Server section, on the gh extension install line that passes --hostname. Check the gh_extension_install manual to confirm the URL form the issue describes, then change that one line so the GHES host is given as part of the repository URL. Done means the line no longer uses --hostname, the rest of the GHES block is unchanged, and the optional gh aw --version example is updated to match the current release.

Written by the indexing model from the issue text.

Description

documentation

Workshop file reviewed

workshop/side-quest-06-01-install-troubleshooting.md

Problem

The "GitHub Enterprise Server (GHE/GHES) endpoint" section instructs learners to run:

gh extension install github/gh-aw --hostname ghes.example.com

gh extension install does not support a --hostname flag. Per the official gh CLI manual (gh_extension_install), the only flags are --force and --pin. GHES installs are done by passing the repository as a full URL instead of OWNER/REPO:

"For GitHub repositories, the repository argument can be specified in OWNER/REPO format or as a full repository URL. The URL format is useful when the repository is not hosted on github.com."

Example from the manual: `gh extension install (my.ghes.com/redacted)

As written, the documented command will fail with an "unknown flag" error for anyone following the GHES troubleshooting path.

Current correct syntax

gh config set git_protocol https --host ghes.example.com
gh auth login --hostname ghes.example.com --scopes "repo,read:org,workflow"
gh extension install (ghes.example.com/redacted)
gh auth status --hostname ghes.example.com

Suggested fix

Replace the line:

gh extension install github/gh-aw --hostname ghes.example.com

with:

gh extension install (ghes.example.com/redacted)

Minor secondary note

The checkpoint line "gh aw --version prints a version number (for example, gh-aw 1.x.x)" shows an example format (1.x.x) that doesn't match the project's current pre-1.0 versioning (latest release is v0.89.21) or the output format shown elsewhere in the workshop (e.g. gh-aw version 0.81.6). Consider updating the example to something like gh-aw version 0.89.21 for consistency, though this is lower priority than the --hostname flag fix above.

Reference

Official gh CLI manual: https://cli.github.com/manual/gh_extension_install

Generated by 🔍 Workshop Sync Check · copilot · auto · 173.7 AIC · ⌖ 0.605 AIC · ⊞ 9.2K · ◷

  • expires on Oct 15, 2026, 4:57 AM UTC
Dominant language
JavaScript
Stars
53
Forks
35
Avg merge
1d 5h
Merged PRs (30d)
16

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-aw-workshop

All issues in githubnext/gh-aw-workshop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.