-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
feat: Add osxSign.continueOnError
option
#1579
Conversation
Thanks for opening a pull request! Here are some highlighted action items that will help get it across the finish line, from the
Development and triage is community-driven, so please be patient and we will get back to you as soon as we can. |
793c041
to
037a77b
Compare
Codecov Report
@@ Coverage Diff @@
## main #1579 +/- ##
==========================================
+ Coverage 95.58% 95.73% +0.14%
==========================================
Files 15 15
Lines 793 797 +4
==========================================
+ Hits 758 763 +5
+ Misses 35 34 -1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
8567d21
to
454a530
Compare
454a530
to
646279f
Compare
osxSign.continueOnError
optionosxSign.continueOnError
option
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.
LGTM
Thanks for your contribution! 🎉 |
🎉 This PR is included in version 18.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summarize your changes:
Currently there is no way to know that signing on osx failed other than reading the output. This adds an option
continueOnError
(defaults to current behavior,true
) one can set to fail the build if there was an error while signing the app.