-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically produce all binaries for releases from GitHub Actions #106
Conversation
…ction to publish binary artifacts
…list files in `bin` folders
- name: Upload the cmake Linux binary artifacts | ||
uses: svenstaro/upload-release-action@v2 | ||
with: | ||
repo_token: ${{ secrets.GITHUB_TOKEN }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain the work flow here? I'm not very good at git action.
Should I set a secrets.GITHUB_TOKEN ?
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, that is provided, pulled in by GitHub Actions. The action and binaries for release are only produced when you go and actually create an release tag.
As i have here: https://github.com/techno-express/p7zip/releases
This is from https://github.com/marketplace/actions/upload-files-to-a-github-release
Thanks! ; ) |
In reference to https://github.com/jinfeihan57/p7zip/issues/105.
Having a Apple Mac is not necessary, the binaries are already being produced and tested on macOS platform. It seems the project here was uploading the binaries, when there is really no need for that, plus this is more secure.