-
Notifications
You must be signed in to change notification settings - Fork 686
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
Upload should fail if the zipball would be empty and allow-empty-zipball is not true #47
Comments
The behavior has changed pretty significantly. With With A separate option to error out if no files are found seems pretty limited so I think a warning + no artifact is a good way of letting users know that they are in fact not uploading anything. |
I think it would be better to make this an error instead of a warning. Is there a reason for wanting a job that doesn't act as expected to succeed? |
I'm going to close this issue since the path not finding files is an indication of some user error and there is a clear warning now. If you still think that there should be an option to fail the upload if no files are found, I would open another issue here. Instead of |
I would like the option of failing the run instead of posting a warning if the file specified is not found. Should I create a separate issue for it @konradpabjan ? |
Sorry for the noise a minute ago. Yes, I think the "If you still think that…" sentence was meant as you should open a new issue. |
While it was my fault that my Github action started to make empty zipballs, I would have preferred to be alerted of my bug way earlier. Therefor I suggest we add an option
allow-empty-zipball
, and unless that is explicitly set totrue
, we let the upload fail if the zipball would turn out empty.The text was updated successfully, but these errors were encountered: