[workshop-sync] side-quest-06-02-cca-codespace.md: broken cross-reference and risky install order for org-owned Codespaces
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, shell
- Domain
- documentation
Research direction
Start with workshop/side-quest-06-02-cca-codespace.md, then compare the referenced steps in workshop/06-install-gh-aw.md, workshop/02a-setup-codespace.md, and workshop/side-quest-06-01-install-troubleshooting.md. Verify that the Codespace link resolves to the stated section and that the documented install order matches the org-owned Codespaces guidance.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-06-02-cca-codespace.md
Problem
The "Open a Codespace" instructions say:
From Step 6, select the Codespaces button in the
Open a Codespace first (GitHub Copilot Cloud Agent users) section.
workshop/06-install-gh-aw.md currently has no such section or heading ("Open a Codespace first (GitHub Copilot Cloud Agent users)") and no Codespaces button. That file only lists a prerequisite link to Set Up a Codespace under "Before You Start". This is a broken cross-reference that will leave CCA-journey learners unable to find the described button.
Additionally, this side quest's "Install gh-aw in the Codespace terminal" section leads with:
gh extension install github/gh-aw
as the primary install command. But 06-install-gh-aw.md itself states: "In org-owned Codespaces the GitHub token is scoped to the org and cannot access the extension marketplace, so the curl script is the reliable path," and side-quest-06-01-install-troubleshooting.md has a dedicated "Organization Codespace token limitation (HTTP 403)" section describing exactly this failure. Since CCA users are commonly working in org-owned Codespaces, leading with gh extension install risks an avoidable HTTP 403 for this exact audience.
Current correct behaviour
06-install-gh-aw.mdhas no "Open a Codespace first" button/section to link to; the actual Codespace-launch step is02a-setup-codespace.md("Open the Codespace").- The install script (
curl -sL https://raw.githubusercontent.com/github/gh-aw/main/install-gh-aw.sh | bash) is the workshop's documented reliable path for org-owned Codespaces.
Suggested fix
- Update the "Open a Codespace" step to link to
02a-setup-codespace.md#open-the-codespace(or add the referenced button/section to06-install-gh-aw.mdif one is intended to exist there). - Reorder the install instructions to lead with the curl install script as primary, keeping
gh extension install/gh extension upgradeas the fallback for non-org-owned Codespaces, consistent with06-install-gh-aw.mdandside-quest-06-01-install-troubleshooting.md.
Generated by 🔍 Workshop Sync Check · copilot · auto · 158.7 AIC · ⌖ 6.75 AIC · ⊞ 8.2K · ◷
- expires on Sep 30, 2026, 8:58 AM UTC
- Dominant language
- JavaScript
- Stars
- 51
- Forks
- 23
- Avg merge
- 9h 44m
- Merged PRs (30d)
- 25
Getting set up
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-workshop
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
githubnext/gh-aw-workshop#3968 ·
Maintainers usually reply within 1 day
-
agentic-workflows documentation workflow-editor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#3966 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-workshop#3964 ·
Maintainers usually reply within 1 day
-
documentation guidelines
Difficulty 1/5 Under an hour Newbie friendliness 95/100
githubnext/gh-aw-workshop#3959 ·
Maintainers usually reply within 1 day
-
documentation guidelines
Difficulty 1/5 Under an hour Newbie friendliness 90/100
githubnext/gh-aw-workshop#3960 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
refactor
Difficulty 2/5 Half a day Newbie friendliness 84/100
Maintainers usually reply within 5 days
-
translation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ciderapp/translations#87 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
component: split-view platform: windows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
zen-browser/desktop#15616 · 1 reaction ·
Maintainers usually reply within 1 day