Skip to content

fix(link): respect -y/--no-interactive flag#7

Open
TylerStaplerAtFanatics wants to merge 2 commits into
tstapler:masterfrom
TylerStaplerAtFanatics:fix/link-no-interactive-flag
Open

fix(link): respect -y/--no-interactive flag#7
TylerStaplerAtFanatics wants to merge 2 commits into
tstapler:masterfrom
TylerStaplerAtFanatics:fix/link-no-interactive-flag

Conversation

@TylerStaplerAtFanatics

Copy link
Copy Markdown

Summary

The link command passed the --no-interactive (-y) flag value straight through as interactive=, inverting the logic — so -y enabled the "Are these the correct files?" confirmation prompt instead of suppressing it. In a non-tty context (e.g. an Ansible/bootstrap run with stdin redirected) the prompt then aborted with Input is not a terminal / Aborted!.

Changes

  • cfgcaddy/__main__.py: pass interactive=not no_interactive so -y runs non-interactively.
  • Bump version 0.1.80.1.9 so uv tool install picks up the new build instead of reusing the cached wheel for the same version.

Testing

  • cfgcaddy link -y </dev/null now links without prompting and exits 0.
  • Verified end-to-end via an Ansible dotfiles role run: PLAY RECAP ... failed=0, link task ok.

🤖 Generated with Claude Code

tstapler and others added 2 commits June 17, 2026 14:12
The link command passed the --no-interactive flag value directly as
interactive=, inverting the logic — so -y enabled the confirmation
prompt instead of suppressing it. In a non-tty context (e.g. an Ansible
run) the prompt then aborted with "Input is not a terminal".

Pass interactive=not no_interactive so -y runs non-interactively.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Distinguish the -y/--no-interactive flag fix from 0.1.8 so uv installs
the new build instead of reusing the cached wheel for the same version.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants