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 Jun 27, 2023. It is now read-only.
As far as I have understood this GitHub Action allows to produce fixed wheels and push it automatically to public registry. I wonder if we could take the output of this build process and upload it to private registries, for instance, or to produce artifacts that we could use with actions/upload-artifact@v1. Any ideas?
The text was updated successfully, but these errors were encountered:
This action only builds the wheels. They can then be uploaded using e.g. Twine in a next workflow step. Similarly, you can append any actions, and do with the wheel files what you want. In the current version (v0.2.2), the wheels are placed in the wheelhouse directory.
For example, you can use the upload-artifact action, as you suggested, by adding this step:
As far as I have understood this GitHub Action allows to produce fixed wheels and push it automatically to public registry. I wonder if we could take the output of this build process and upload it to private registries, for instance, or to produce artifacts that we could use with actions/upload-artifact@v1. Any ideas?
The text was updated successfully, but these errors were encountered: