feat: use gh to release #66
Conversation
| files: ${{ steps.info.outputs.artifacts_dir }}/* | ||
| GH_TOKEN: ${{ github.token }} | ||
| run: | | ||
| gh release upload ${{ github.ref_name }} ${{ steps.info.outputs.artifacts_dir }}/* |
There was a problem hiding this comment.
Should we make it a prerelease to align with the original code?
There was a problem hiding this comment.
I think we don't need to do it. It only uploads tarball when we create a release like this test https://github.com/Yu-Jack/docker-machine-driver-harvester/releases.
There was a problem hiding this comment.
@FrankYang0529 do we need prerelease set to true?
There was a problem hiding this comment.
Some of previous releases were created by github-actions. Probably, it's better to create a draft release first and manually change to latest release.
There was a problem hiding this comment.
It depends on tag or release. If we prefer to create a tag first, then we can use draft release. If we prefer to create a release directly, then we don't need to use this action to create a draft release. But, I just modified my codes to support creating a draft release.
Yu-Jack
force-pushed
the
HARV/60
branch
2 times, most recently
from
6a20dee to
9e31d5e
Compare
Signed-off-by: Jack Yu <[email protected]>
No description provided.