Automate release with GitHub Action Job #121
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
leegeth
reviewed
Dec 3, 2020
| git submodule update --init --checkout --recursive | ||
| - name: Create ZIP | ||
| run: | | ||
| zip -r coreMQTT-${{ github.event.inputs.version_number }}.zip coreMQTT -x "*.git" |
There was a problem hiding this comment.
This will leave the .github folder in the zip. We were not doing that for the prior releases. I think it is better to avoid it.
The command can be modified to do that
zip -r coreMQTT-${{ github.event.inputs.version_number }}.zip coreMQTT -x "*.git*"
aggarw13
commented
Dec 4, 2020
leegeth
approved these changes
Dec 4, 2020
cobusve
approved these changes
Dec 4, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a GitHub Action job to trigger a release process which includes operations of:
The workflow can be manually triggered and takes the input values of Commit ID (to create a release for) and the Version string for tagging the release with
Testing
Here is an example run of the release job on my fork repository:
https://github.com/aggarw13/coreMQTT/actions/runs/399119805.
It pushed the test tag (
test-v2) and created a release along with the release asset on the repository: https://github.com/aggarw13/coreMQTT/releases/tag/test-v2