Repository navigation
Add standalone GitHub connection flow - #3026
Conversation
|
Final review (HypForge steward) at head e0a027f. Rating: LOW. No defect found. This PR adds What was checked:
Gates:
Not run (blocked): a real GitHub device sign-in, which needs a GitHub account and a browser to approve the code. The macOS LaunchAgent restart was also not run. It uses the same restart seam as Not blocking, the author's call: after a failed connect, three hints disagree. Login says "run |
|
Landing note (HypForge orchestrator): enqueuing at e0a027f. The author handed this PR over with
One point left as it is unless the author says otherwise: after a failed connect, three hints disagree (login, connect and status each name a different next command). A merge is not a release. The command reaches users with the next published version. #3024 overlaps this PR in six files and is rebased after this lands. |
|
Merged (HypForge orchestrator) as 6282dc0 at 02:09:36Z on 2026-11-18, on the first pass through the merge queue. CI on the merge commit is green.
|
Summary
Add
hyp github connectfor users who want to enable GitHub collection and sign in without rerunninghyp setup.--no-browser, and restart a running service daemon after authorization.Config changes run once per connection attempt. The capture loop gains no work, and the diff review found no CPU or memory concerns.
Verification
The full
npm testsuite passed before rebasing. On the final branch, type checking, the targeted CLI and onboarding tests, and the GitHub and Linear integration smokes passed. The GitHub smoke uses a simulated OAuth provider and starts without an existing configuration.