docs: document the server-proxied GitHub device flow - #49
Conversation
The README's Credentials and Configuration sections still described the earlier exchange, where the CLI ran the device flow itself and handed this server a raw GitHub access token. Bring them in line with the two-route shape that replaced it: the API table, the two routes' own paragraphs, the closed provenance gap, the byte-identical refusal now covering both routes and its new shapes, the accepted device-code quota abuse, the replaced-exchange breaking change, and the "Enable Device Flow" deployment step. PublishSkill/SKILL.md needs no change - it documents `stele auth login` as the user's step and says nothing about token mechanics, and PublishSkillTests (unaffected by this commit, since it reads PublishSkill.swift rather than README.md) is still green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LBzRbsSw9JzfEg1p3a3FVo
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Free Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/settings/billing. Comment |
The README's Credentials and Configuration sections still described the earlier exchange, where the CLI ran the device flow itself and handed this server a raw GitHub access token. Bring them in line with the two-route shape that replaced it: the API table, the two routes' own paragraphs, the closed provenance gap, the byte-identical refusal now covering both routes and its new shapes, the accepted device-code quota abuse, the replaced-exchange breaking change, and the "Enable Device Flow" deployment step.
PublishSkill/SKILL.md needs no change - it documents
stele auth loginas the user's step and says nothing about token mechanics, and PublishSkillTests (unaffected by this commit, since it reads PublishSkill.swift rather than README.md) is still green.Tests: just build clean; just test: 424 tests in 38 suites, all passing — including PublishSkillTests, which is the suite this PR claims needs no change.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LBzRbsSw9JzfEg1p3a3FVo
Stack created with GitHub Stacks CLI • Give Feedback 💬