Skip to content

Different commands use different flags for auto-confirmation #977

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
elhimov opened this issue Oct 9, 2024 · 0 comments
Open

Different commands use different flags for auto-confirmation #977

elhimov opened this issue Oct 9, 2024 · 0 comments
Assignees
@elhimov
Labels
1sp code health Improve code readability, simplify maintenance and so on teamE

Comments

@elhimov
Copy link
Contributor

elhimov commented Oct 9, 2024 •
edited
Loading

Below are excerptions related to force-flags from the kill, clean, stop and restart commands:

  -f, --force   do not ask for confirmation
  -f, --force   do not ask for confirmation
  -y, --yes    Automatic yes to confirmation prompt
  -y, --yes    Automatic yes to confirmation prompt

Consider using the single approach (for example -f, --force flags).
@oleg-jukovec oleg-jukovec added 1sp teamE code health Improve code readability, simplify maintenance and so on labels Oct 10, 2024
@elhimov elhimov changed the title Different commands use different flags to suppress user confirmation (force-semantic) Different commands use different flags for auto-confirmation Nov 11, 2024
@elhimov elhimov self-assigned this Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@elhimov elhimov

Labels
1sp code health Improve code readability, simplify maintenance and so on teamE
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@oleg-jukovec @elhimov
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy