The bootstrap still stops for prompts
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 56/100
Research direction
Start by reading install/bootstrap.zsh, then inspect install/git, install/gh, and each install/* script that calls a third-party installer. Run a headless bootstrap in a tart VM to identify remaining prompts. Done means sudo is requested once, installer prompts are disabled where supported, and install/gh explains when it skips upgrades because authentication is unavailable.
Written by the indexing model from the issue text.
Description
A full run of install/bootstrap.zsh is not yet hands-off. These are the places it waits for a person, from the first complete headless run in a tart VM.
sudo, three times. The Command Line Tools install runs softwareupdate -i under sudo. install/git runs git lfs install --system under sudo. The Determinate Nix installer asks for sudo too. Each one prompts on the terminal and the run sits there until the password is typed.
Tool installers with their own questions. The atuin installer asked four questions: history import, cloud sync, Atuin AI, and the daemon. The installer has a --non-interactive flag and the bootstrap now passes it, so those four are gone. Other installers may have the same shape and have not been audited for it.
Noise that looks like a prompt. install/gh runs gh extension upgrade --all, which prints the gh auth login advice on a machine that is not logged in. It does not stop the run, but it reads as if it did.
Options for the sudo prompts
- Ask for sudo once at the start, with
sudo -v, and keep the timestamp alive in the background for the length of the run. The three later prompts then never appear. The password is still typed once, by a person. - Or accept three prompts and document them as the places the run pauses.
Asking once is the better experience and changes nothing about what runs as root.
For the rest
- Audit every
install/*that calls a third-party installer for a non-interactive flag and pass it. - Have
install/ghskip the upgrade whengh auth statusfails, with one line saying why.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 0
- Avg merge
- 14h 36m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from indexzero/dotfiles
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 39/100
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
All issues in indexzero/dotfiles
Similar issues
-
roadmap-100
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day
-
priority: medium status: needs-decision work-class: scoped
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melodic-software/claude-code-plugins#9339 · 2 comments ·
Maintainers usually reply within 1 day
-
数据界面的横向滚动条缺失Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
zilliztech/attu#1037 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
community-scripts/ProxmoxVE#18073 · 1 comment ·
Maintainers usually reply within 1 day
-
Uptime "Test Monitor" always fails with an empty HTTP 400 (uptime-checker API endpoint not configured)Possibly taken @ayoubjemai claimed this today. OpenWaiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
getsentry/self-hosted#4582 ·
Maintainers usually reply within 1 day