Skip to content

Conversation

@ntheanh201
Copy link
Collaborator

Describe your changes

Merge Vietnamese development branch into main.

Related issue number or link (ex: resolves #issue-number)

Checklist before opening this PR (put x in the checkboxes)

  • This PR does not contain plagiarism
    • don’t copy other people’s work unless you are quoting and contributing it to them.
  • I have signed off on all commits
    • signing off (ex: git commit -s) is to affirm that commits comply DCO. If you are working locally, you could add an alias to your gitconfig by running git config --global alias.ci "commit -s".

thuanpham582002 and others added 15 commits May 10, 2025 11:17
Signed-off-by: trungphuongtt <[email protected]>
Signed-off-by: Trung Thi Phuong <[email protected]>
Co-authored-by: The Anh Nguyen <[email protected]>
@netlify
Copy link

netlify bot commented May 27, 2025

Deploy Preview for cncfglossary ready!

Name Link
🔨 Latest commit fdd591e
🔍 Latest deploy log https://app.netlify.com/projects/cncfglossary/deploys/683d600d5440b200089b6fd4
😎 Deploy Preview https://deploy-preview-3523--cncfglossary.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions bot added the lang/vi for Vietnamese label May 27, 2025
@jihoon-seo jihoon-seo added the maintainers Use this label if PR requires maintainers to take action label May 28, 2025
Copy link
Collaborator

@jihoon-seo jihoon-seo left a 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.

@thuanpham582002
Copy link
Collaborator

add new term to follow up:

#3519

Copy link
Collaborator

@Okabe-Junya Okabe-Junya left a 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:

  1. I opened the PR to sync main <-> dev-vi. Before moving forward with this PR, let's merge this one
    a. #3525
  2. How to handle DCO fails (Do we need to bypass this again?)

@Okabe-Junya
Copy link
Collaborator

We might bypass the DCO check again, like we did in the PR #3484.

It looks good option for this PR, but we need to discuss about this problem for future...

[maintain] Merge main into dev-vi
@seokho-son
Copy link
Collaborator

@jihoon-seo @Okabe-Junya
I believe there is no additional difference regarding the DCO issue in this PR, given the decision made in #3484 (comment) .

The cause of the DCO issue is the same as explained in #3484 (comment)
, and it will likely continue unless all contributors adjust their Git settings accordingly or avoid using the "Apply suggestion" button in the GitHub UI.

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)

Copy link
Collaborator

@seokho-son seokho-son left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@seokho-son seokho-son merged commit f50b799 into main Jun 11, 2025
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lang/vi for Vietnamese maintainers Use this label if PR requires maintainers to take action

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants