chore: implement the Publish Tag workflow #11
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.
Description
This PR introduces the
publish-tag.yml
workflow. Its purpose is to extract the version value from theversion.json
file and create a new tag when a commit is merged into the main branch or triggered manually.What type of PR is this? (check all applicable)
Related Tickets & Documents
https://github.com/gs-gs/fa-ag-trace/issues/872
Mobile & Desktop Screenshots/Recordings
Triggering the
publish-tag.yml
workflow:The created tag:
In cases where the tag already exists:
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?