Repository navigation
Stop telling people to visit a URL that 404s - #14
Merged
Merged
Conversation
Every "get an API key" message pointed at https://bootintel.com/settings/api-keys. That page does not exist and never has: there is no /settings route on the site at all. Keys live at /dashboard/developer. Six places said otherwise: doctor, whoami twice, scan --api twice, and analyze --api. It surfaced because someone ran `bootintel doctor` on a Mac and pasted the output. That line had presumably been wrong for as long as it existed, and no test could have caught it: it is a string, and the route it names is in a different repo. The advice was also stale in a way I introduced. API-key auth is gated at Pro, so for anyone below that tier the instruction was not merely a broken link but the wrong action entirely. These messages now recommend `bootintel login` first, which is the path for a person at a terminal, and mention keys as the CI and scripting option they are. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Rewriting the --api message dropped the ${API_KEY_ENV} interpolation, which
made the constant dead code and broke clippy under -D warnings. Naming the
variable is useful to the reader anyway, so it goes back in the message rather
than the constant coming out.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every "get an API key" message pointed at
https://bootintel.com/settings/api-keys. That page does not exist and never has — there is no/settingsroute on the site at all. Keys live at/dashboard/developer.Six places said otherwise:
doctor,whoami(twice),scan --api(twice), andanalyze --api.It surfaced because someone ran
bootintel doctoron a Mac and pasted the output. That line had been wrong for as long as it existed, and no test could have caught it: it is a string, and the route it names lives in a different repo.The advice was also stale in a way introduced by the login work. API-key auth is gated at Pro, so for anyone below that tier the instruction was not just a broken link but the wrong action. These messages now recommend
bootintel loginfirst, which is the path for a person at a terminal, and mention API keys as the CI and scripting option they are.Tests, clippy under
-D warnings, and rustfmt all clean.