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
Rather than using the GitHub recommended, although third-party action for drafting a release and uploading files to it in .github/workflows/build.yml, use the default (although archived) actions provided in the actions repository for GitHub Actions:
Alternatively, rather than relying on archived actions projects, it seems that a solution can be put together manually based on the options mentioned here:
For reference on configuring the third-party action mentioned at the start of this issue, see the block below (which on initial test did not work - the step was skipped in the build even though a tag was pushed):
- name: Draft Release# See more information about this step at https://github.com/softprops/action-gh-releaseuses: softprops/action-gh-release@v1if: startsWith(github.ref, 'refs/tags/')with:
draft: trueprerelease: truegenerate_release_notes: truefail_on_unmatched_files: truefiles: | ./exec/cfs-linux ./exec/cfs-macos ./exec/cfs-win.exe
The text was updated successfully, but these errors were encountered:
khalidx
changed the title
Investigate using official GitHub Actions for drafting a release
Investigate using official actions for drafting a release
Apr 26, 2022
Rather than using the GitHub recommended, although third-party action for drafting a release and uploading files to it in
.github/workflows/build.yml
, use the default (although archived) actions provided in the actions repository for GitHub Actions:Alternatively, rather than relying on archived actions projects, it seems that a solution can be put together manually based on the options mentioned here:
For reference on configuring the third-party action mentioned at the start of this issue, see the block below (which on initial test did not work - the step was skipped in the build even though a tag was pushed):
The text was updated successfully, but these errors were encountered: