-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
✨ Check review-state in build:wait #1205
Conversation
Thanks for the contribution, we'll review it in some time. |
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.
back to you @AaronBuxbaum
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.
Nice @AaronBuxbaum!
I've left some additional comments, post which we're gtg
@itsjwala ready to go! Not sure how, but I was seeing these tests fail:
I updated them to pass, but give them a look and make any updates desired. then we can push this across the finish line. It might just be my local configuration! |
based on CI, it looks like it might be my local configuration. Made a commit to remove those changes. |
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.
Thanks for your contribution @AaronBuxbaum 🔥
Merging this PR (windows CI are known to be flaky) , This will be part of 1.21.0
release ETA end of week.
build:wait
when used with--fail-on-changes
exits CLI with non-zero code, when the build is approved, ideally we'd want to exit 0--pass-if-approved
which will exit 0 when the build is approved even when diffs are found.--fail-on-changes
is passed