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
When a release is made in GitHub we should be publishing a release binary as an artefact associated with that release.
💬 Task Description
Create a release workflow that is triggered by the creating of a GitHub release.
Build the asc binary, package it (with the documentation) into a asc-x86_64-apple-macosx-${RELEASE_TAG}.zip and upload it to the release as an asset using upload-release-asset.
The text was updated successfully, but these errors were encountered:
Wanted to chime in to say that this would be super helpful for CI/CD scenarios. Currently I'm using this cli to download provisioning profiles for my iOS app in order to sign and upload the app. Needing to build the CLI from source adds ~5 minutes to each run
❕ Problem Statement
When a release is made in GitHub we should be publishing a release binary as an artefact associated with that release.
💬 Task Description
release
workflow that is triggered by the creating of a GitHub release.asc
binary, package it (with the documentation) into aasc-x86_64-apple-macosx-${RELEASE_TAG}.zip
and upload it to the release as an asset using upload-release-asset.The text was updated successfully, but these errors were encountered: