-
Notifications
You must be signed in to change notification settings - Fork 75
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
Automate release with GitHub Action job #78
Conversation
@@ -163,7 +163,11 @@ typedef struct NetworkContext NetworkContext_t; | |||
* @param[in] pBuffer Buffer to receive the data into. | |||
* @param[in] bytesToRecv Number of bytes requested from the network. | |||
* | |||
* @return The number of bytes received or a negative error code. | |||
* @return The number of bytes received or a negative value to indicate |
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.
Is this change mentioned in the commit message?
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.
Nope, but this change was just to satisfy the SSoT CI check between transport_interface.h
files of coreMQTT and coreHTTP
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/coreHTTP/runs/1512507665?check_suite_focus=true
It pushed the test tag (
test-v2
) and created a release along with the release asset on the repository: https://github.com/aggarw13/coreHTTP/releases/tag/test-v3