Repository navigation
Let the Homebrew installer in bootstrap ask for the password - #2
Merged
Merged
Conversation
With NONINTERACTIVE=1 the installer only tries `sudo -n`, so on a fresh Mac without cached sudo credentials it aborts instead of prompting. Run it interactively and say in the README that it asks for the password, and that `xcode-select --install` comes first so git can clone the repo. Co-Authored-By: Claude Opus 5.5 <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
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.
What changed
bin/bootstrapruns the Homebrew installer interactively instead of withNONINTERACTIVE=1, and tells you it will ask for your password and for Enter.xcode-select --installfirst, sogitexists to clone the repo, and that Homebrew asks for the password once.Why
With
NONINTERACTIVE=1, the Homebrew installer only triessudo -n, which never prompts. On a fresh Mac without cached sudo credentials, it aborts with "Insufficient permissions" instead of asking for the password. So far the workaround was runningsudo -vbefore bootstrap.When you run bootstrap yourself from a terminal, the installer is now interactive. It still switches to non-interactive mode on its own when its input isn't a terminal or
CIis set.Testing
shellcheck bin/bootstrappasses.sudo -v, which prompts.🤖 Generated with Claude Code