action "generate" in fork always aborts in step "upload pinouts"

[mi-hol]

Is below abort caused by a missing setting in forked repo or is logic for forked repo required in action definition? Storing output of build in local repo fork or separate location from official destination would be great for validation purposes. Maybe a good example is this

[rusefillc]

Both.

Ideally actions would be smart enough to detect a fork and not attempt to upload

@chuckwagoncomputing any change to get you involved?