Replies: 1 comment
|
Sorry for the late response--if there are no changes to publish, it's the expected behavior that beachball will do nothing and exit successfully. Why do you want it to fail in that case? |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
In my case, I'm publishing a package on schedule. but if there are no features or bugfixes has been merged in only some DevOps related code changes are there then it should fail at the stage of publishing by saying that there are no changes in packages. but it is not happening. Is there any specific flag or option that we need to enable to fail the process at that step?
All reactions