-
Notifications
You must be signed in to change notification settings - Fork 576
Merge dev-vi into main #3523
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
Merge dev-vi into main #3523
Conversation
Signed-off-by: thuanpham582002 <[email protected]>
Signed-off-by: thuanpham582002 <[email protected]>
Signed-off-by: thuanpham582002 <[email protected]>
) Signed-off-by: thuanpham582002 <[email protected]>
Signed-off-by: thuanpham582002 <[email protected]>
Signed-off-by: trungphuongtt <[email protected]>
Signed-off-by: thuanpham582002 <[email protected]>
Signed-off-by: thuanpham582002 <[email protected]>
Signed-off-by: trungphuongtt <[email protected]> Signed-off-by: Trung Thi Phuong <[email protected]> Co-authored-by: The Anh Nguyen <[email protected]>
Signed-off-by: trungphuongtt <[email protected]>
#3518) Signed-off-by: trungphuongtt <[email protected]>
…3503) Signed-off-by: thuanpham582002 <[email protected]>
…3504) Signed-off-by: thuanpham582002 <[email protected]>
Signed-off-by: thaomike <[email protected]>
Signed-off-by: Nguyen Danh Huan <[email protected]>
✅ Deploy Preview for cncfglossary ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jihoon-seo
left a comment
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.
The commit history of this PR is so neat (all the PRs are squash-merged and all the commit messages have nice consistency), and I like it!
But I cannot find why the DCO check fails, since it seems that all the PR have proper DCO signatures.
We might bypass the DCO check again, like we did in the PR #3484.
|
add new term to follow up: |
Okabe-Junya
left a comment
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.
Thank you for all your contributions, great work!!
Almost LGTM, but let me confirm two things:
- I opened the PR to sync main <-> dev-vi. Before moving forward with this PR, let's merge this one
a. #3525 - How to handle DCO fails (Do we need to bypass this again?)
It looks good option for this PR, but we need to discuss about this problem for future... |
[maintain] Merge main into dev-vi
|
@jihoon-seo @Okabe-Junya The cause of the DCO issue is the same as explained in #3484 (comment) Let me set bypass DCO check for this PR as well based on the same decision made in #3484 (comment) to not blocking localization team activity. In the meantime, the maintainers should consider establishing a clear policy for handling DCO checks. (for instance, we can make DCO check exception for every PRs related with dev-xx branches) |
seokho-son
left a comment
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.
LGTM!
Describe your changes
Merge Vietnamese development branch into main.
Related issue number or link (ex:
resolves #issue-number)Checklist before opening this PR (put
xin the checkboxes)git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to yourgitconfigby runninggit config --global alias.ci "commit -s".