A 0ea2692e1e fix(github-auth): always run gh setup when user explicitly opts in (#2674) ... When the user selects the GitHub CLI step in setup options (interactive prompt or --steps github), offerGithubAuth() was silently returning early if no local gh token was found by detectGithubAuth(). This made the step unreachable for users without gh installed locally — exactly the ones who need remote setup most. Fix: accept an `explicitlyRequested` parameter in offerGithubAuth(). When true, skip the githubAuthRequested guard and always run the remote install. The orchestrator passes enabledSteps?.has("github") as this flag. detectGithubAuth() still auto-enables the step when a local token exists (convenience forwarding), but can no longer block a user-explicit request. Fixes #2672 Agent: issue-fixer Co-authored-by: B <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>		2026-03-15 22:19:38 -07:00
..
cli	fix(github-auth): always run gh setup when user explicitly opts in (#2674)	2026-03-15 22:19:38 -07:00
shared	feat: add downloadFile to CloudRunner + local OpenClaw config merge (#2636)	2026-03-14 15:47:32 -07:00