You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 4, 2022. It is now read-only.
Hello, Could you add a confirmation input similar to $ git send-email for gh issue foo? So in order to open new issue you should type y or n to reject. Also a flag -y to run it non-interactively.
The text was updated successfully, but these errors were encountered:
@protoEvangelion, I'm not sure about other use cases, because e.g. commenting on an issue requires to type a specific flag. But to be more identical in commands for online activity which creates something on GitHub a necessity of -y flag to send without asking is a good idea.
I'm sure it would be nice in case of gh pull-request MESSAGE and gh issue MESSAGE.
Hmm... I definitely like the pattern of using -y for non interactive mode, but I would be hesitant to change the UX to require user feedback for each main action like sending PRs or creating new issues.
The main reason for that is because a lot of people use gh ... in aliases or scripts and this type of functionality would break their scripts if they don't include -y.
The main reason for that is because a lot of people use gh ... in aliases or scripts and this type of functionality would break their scripts if they don't include -y.
Any ideas on how to overcome that challenge?
I think we could have a release with a warning to give people some time for a switch to new syntax. E.g.: “gh pull-request MESSAGE, gh issue MESSAGE, gh … commands syntax will change in a feature release, requiring you to specify -y flag to send non-interactively”
Hello, Could you add a confirmation input similar to
$ git send-email
forgh issue foo
? So in order to open new issue you should typey
orn
to reject. Also a flag-y
to run it non-interactively.The text was updated successfully, but these errors were encountered: