Closed ezet closed 3 years ago
No star, no option.
When you have an errors or warnings during publishing, eventually it will not be published, you will not receive an email from Google confirming that package is published, then you'll go to actions to analyze log details to trace and fix the issues. Build is green because it's not an issues with the package code itself, it's a different category of issues .
BUT When unit tests are green, your code is OK. and afterwards you have an "paranoid" errors or warnings during publishing, Build is RED then you'll open up the actions log and look into the log details to trace and fix the issues.
The only difference between those use cases is the number of RED builds in your repository.
It's not intuitive, to me at least, that the build passes when the publishing fails due to errors or warnings.
Or maybe add an option for it, if you want to keep current behavior for some reason?