Respect "No, don't ask again" for the shell-completion prompt
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
Start at the shell-completion prompt and the standard global settings handling used by cf commands. Reproduce the prompt across new processes and working directories, then inspect how temporary and permanent declines, resets, non-interactive execution, and settings write failures are represented. Done means the acceptance scenarios pass with focused tests for each behavior.
Written by the indexing model from the issue text.
Description
Problem
The CLI can repeatedly ask whether to enable shell completion even after the user selects “No, don't ask again.” Repeating the prompt on every command makes the preference ineffective and disrupts normal use.
Reproduction
- Run a command that displays the shell-completion prompt.
- Select “No, don't ask again.”
- Run another
cfcommand.
The prompt appears again.
Expected behavior
Persist the opt-out in the standard global settings location and do not show the prompt again unless the user explicitly resets that preference.
Acceptance criteria
- The opt-out survives new processes and working directories.
- Declining once without the permanent option retains the intended temporary behavior.
- Read-only or unwritable settings locations produce a single actionable warning.
- Non-interactive and CI environments never display the prompt.
- Tests cover opt-in, one-time decline, permanent decline, reset, and persistence failure.
- Dominant language
- TypeScript
- Stars
- 853
- Forks
- 42
- Avg merge
- 17h 57m
- Merged PRs (30d)
- 146
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 cloudflare/cf
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
cloudflare/cf#344 ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cf#262 ·
Maintainers usually reply within 1 day
-
`cf dev` rejects `--port` and `--host` for Vite projects, including the `cf init` templatePossibly taken @jamesopstad claimed this 6 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cloudflare/cf#223 · 2 assignees ·
Maintainers usually reply within 1 day
-
upstream
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cloudflare/cf#179 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
cloudflare/cf#347 ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OpenPetsHQ/openpets#273 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fritzprix/libr-agent#2161 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
blackboardsh/electrobun#581 ·
-
backlog-skill effort:xs frontend infra ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
LucasSantana-Dev/Lucky#2862 ·
Maintainers usually reply within 1 day