[workshop-sync] workshop/side-quest-06-02-cca-codespace.md: misleading authentication doc link
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 84/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, github-actions
- Domain
- documentation
Research direction
Open workshop/side-quest-06-02-cca-codespace.md and inspect the gh auth login sentence. Check whether the linked authentication section covers Codespace browser sign-in, then remove the misleading link or replace it with the GitHub CLI gh auth login documentation. Done when the sentence points to an accurate reference or has no link.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-06-02-cca-codespace.md
Problem
The file says:
If needed, run
gh auth loginand complete browser sign-in.
The #authentication section of the gh-aw Copilot Cloud Agent reference covers authenticating the create-agent-session / assign-to-agent safe outputs (PAT, GitHub App, magic secret). It does not describe gh auth login browser sign-in in a Codespace.
Suggested fix
Remove the link (the gh auth login prompt is self-explanatory), or point to GitHub CLI docs (https://cli.github.com/manual/gh_auth_login) instead.
Other reviewed files (side-quest-05-03-two-file-structure.md, side-quest-06-01-install-troubleshooting.md) had no drift against gh-aw v0.92.0; their doc links and anchors resolve.
Generated by 🔍 Workshop Sync Check · copilot · auto · 22.7 AIC · ⌖ 0.549 AIC · ⊞ 9.2K · ◷
- expires on Oct 21, 2026, 1:40 PM UTC
- Dominant language
- JavaScript
- Stars
- 55
- Forks
- 36
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 17
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
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#4897 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
githubnext/gh-aw-workshop#4896 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4885 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
githubnext/gh-aw-workshop#4878 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
githubnext/gh-aw-workshop#4879 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
status: waiting for maintainer
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
mui/material-ui#49547 ·
Maintainers usually reply within 1 day
-
[2.x] extension-manager: translation keys that changed meaning keep their old namesPossibly taken A pull request linked to this issue is open or already merged. Opentype/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Update to mocha 12.xOpen
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rescript-lang/rescript#8996 ·
Maintainers usually reply within 1 day