chore: add cicd for running unit test when creating PR #180
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 22a3ce7 |
namhoang1604
approved these changes
May 22, 2024
ducpm511
added a commit
that referenced
this pull request
Jun 4, 2024
* next: chore: fix the dockerfile to set entrypoint chore: update vckit Dockerfile (#184) chore: update DockerFile and agent template (#183) fix: bug fix for dockerize (#174) chore: add cicd for running unit test when creating PR (#180) chore: update agent config file (#181) # Conflicts: # pnpm-lock.yaml
This was referenced Jan 17, 2025
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
Related Tickets & Documents
CI CD: #458
Mobile & Desktop Screenshots/Recordings
Configure the pipeline to fail if the code coverage falls below the specified threshold
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?