Release process should only abort when answer is `n`, retry otherwise
aeneasr opened this issue · comments
Preflight checklist
- I could not find a solution in the existing issues, docs, nor discussions.
- I agree to follow this project's Code of Conduct.
- I have read and am following this repository's Contribution Guidelines.
- This issue affects my Ory Cloud project.
- I have joined the Ory Community Slack.
- I am signed up to the Ory Security Patch Newsletter.
Describe the bug
I have already bodged several releases using the ORY CLI because I accidentally pressed a different key than the y
key. In that case, the CLI just aborts the process instead of retrying to get an answer. This can bodge a release mid-process and is very annoying to fix manually.
Reproducing the bug
Do a release (ory dev release publish patch
), press f
instead of n
, see what happens (larry).
Relevant log output
No response
Relevant configuration
No response
Version
master
On which operating system are you observing this issue?
No response
In which environment are you deploying?
No response
Additional Context
Alternative would be to not ask for confirmation after the release has been kicked off? or ask for confirmation BEFORE pushing?