-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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.
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
airbyte-ci: Add --yes option #33206
airbyte-ci: Add --yes option #33206
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that it feels a little dangerous to link a local activity (upgrade the binary) with a remote activity that has downstream effects (publishing) with the same flag. e.g., I'll always want to run with -y
locally to upgrade, but since the same flag means that I also might publish by accident... I guess I won't use it?
@evantahler Fair call out. Personally I wanted to keep a global However I agree with your point of Local vs remote. Safe vs dangerous. So I updated this to have a flag specifically for auto-update. LMK if you thinks its an improvement |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 works for me!
|
Co-authored-by: bnchrch <bnchrch@users.noreply.github.com>
Overview
Add a
-y
option to airbyte-ci to preagree to any prompts