GitHub Action for automatically attaching the mod to a release #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces a new GitHub Actions workflow to automate the process of attaching a mod asset to a release. The workflow is triggered when a release is published by a maintainer, and includes steps to create a zip archive of the release and upload it as an asset.
Example:
Key changes:
.github/workflows/assets-on-release.yml: Added a new workflow that triggers on release publication, creates a zip archive of the release, retrieves the latest release information, and uploads the asset file to the release.Testing: