You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 5, 2020. It is now read-only.
I'm building a debian package, which already has a name and version number created by dpkg-buildpackage. I wouldn't want to specify the path of the package each time a new build rolls out. I've found that v2 of upload-artifacts allow wildcards. It is possible that this is supported by update-release?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm building a debian package, which already has a name and version number created by dpkg-buildpackage. I wouldn't want to specify the path of the package each time a new build rolls out. I've found that v2 of upload-artifacts allow wildcards. It is possible that this is supported by update-release?
The text was updated successfully, but these errors were encountered: