Skip to content

fix: give every confirmation prompt its own skip setting - #7

Merged
KiryuuLight merged 1 commit into
devfrom
issue-2
Jul 27, 2026
Merged

KiryuuLight merged 1 commit into
devfrom
issue-2

Conversation

@KiryuuLight

@KiryuuLight KiryuuLight commented Jul 27, 2026 •

Copy link
Copy Markdown
Contributor

Closes #2.

skip_delete_warning only ever gated one prompt — the alert when you tick a task's delete flag. The run confirmation never read the settings, so there was no way to turn it off.

One opt-out per prompt, lazygit-style:

Key Silences
skip_delete_warning alert when enabling a task's delete flag (unchanged)
skip_run_confirm the run confirmation
skip_remove_confirm removing a profile or task

Also: a single task used to run with no confirmation at all. Now r and R go down the same path, so the prompt depends on what runs rather than how many tasks are selected.

fmt, clippy, 69 tests clean.

The run confirmation appeared whenever more than one task was selected
and never consulted the settings, so there was no way to turn it off. A
single task had no confirmation at all, which made the prompt depend on
how many tasks happened to be selected rather than on what was about to
run.

Route every run through the same check, gated on a new skip_run_confirm
setting, and give profile and task removal the same treatment via
skip_remove_confirm. The run modal can now show a single task, so its
copy handles n == 1.

skip_delete_warning keeps its existing meaning: the alert shown when
enabling a task's delete flag.

Closes #2
@KiryuuLight
KiryuuLight merged commit 1fe0354 into dev Jul 27, 2026
1 check passed
@KiryuuLight
KiryuuLight deleted the issue-2 branch July 30, 2026 12:34
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.

1 participant