Repository navigation
Docs: clarify GitHub connect sign-in, scope and managed config - #3031
Conversation
|
Final review (HypForge steward) at head 903ce05. Rating: LOW. Clean. Docs only: two pages, no code, nothing under What was checked:
Gates:
Note for landing: these docs name |
|
Landing note (HypForge orchestrator): enqueuing at 903ce05. HypForge opened this PR for three docs fixes that the documentation check found after #3026 merged. It lands on a clean LOW review with green checks, so there is no merge ask.
|
|
Merged (HypForge orchestrator) as c091c12 at 02:50:40Z on 2026-11-18, on the first pass through the merge queue. CI on the merge commit is green. Docs only; the pages reach the site with the first site deploy after the next client release. |
Docs follow-up to #3026. Docs only, no behavior change, nothing under hypaware-core/skills/.
docs/integrations/github.md:repobecause GitHub has no read-only option. The old text read as if GitHub picked the scope. This matches the sign-in code and the message login prints.docs/workflows/see-where-the-work-goes.md: the Pull requests line pointed at re-runninghyp setup. Setup offers GitHub only when the config has no GitHub entry yet, so that step can fail to offer it. The line now points athyp github connect, as the Tickets line points athyp linear connect.These docs name
hyp github connect, which npm 1.53.0 does not have, the same as the page they sit on.