add: ci/cd workflow to verify chinese translations #520
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
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Welcome @YashPimple! It looks like this is your first PR to kubeedge/website 🎉 |
kubeedge-bot
added
the
size/S
Signed-off-by: Yash Pimple <yashpimple22@gmail.com>
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.
Fix: #489
Description
This PR implements a Continuous Integration/Continuous Deployment (CI/CD) workflow to ensure the accuracy and completeness of Chinese translations in our project.
Expected Outcome
This workflow aims to maintain consistency between English and Chinese versions of website pages, ensuring that any changes made are reflected accurately in both languages
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No