feat: create git workflow for release tagging and generate the release note #199
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
Coverage reportCaution Coverage does not meet threshold
Test suite run success0 tests passing in 0 suite. Report generated by 🧪jest coverage report action from f836421 |
ldhyen99
reviewed
Jul 1, 2024
huynguyen-hl
approved these changes
Jul 1, 2024
ldhyen99
approved these changes
Jul 4, 2024
namhoang1604
approved these changes
Jul 5, 2024
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.
What type of PR is this? (check all applicable)
Description
This PR is to create a git workflow for release tagging and generate the release note
Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings
Created Tag:
Generated Release note:
Job's logs:
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?