Localize Security Best Practices article to Korean
#3580
+116
−43
Conversation
This file contains hidden or 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
roeniss
reviewed
Jan 11, 2026
Contributor
There was a problem hiding this comment.
Hello, I reviewed the translation from the top then stopped at line 52 (before "## Avoid unwanted changes with protected branches" line) because I realized that the ko/security-best-practices-for-your-project.md and root security-best-practices-for-your-project.md have different text quite a lot.
I think it would be better to continue review after those original english (untranslated) files are updated to the latest version. Let me make another PR for that.
edit) here: #3582
| --- | ||
|
|
||
| Bugs and new features aside, a project's longevity hinges not only on its usefulness but also on the trust it earns from its users. Strong security measures are important to keep this trust alive. Here are some important actions you can take to significantly improve your project's security. | ||
| 버그 수정과 새로운 기능도 중요하지만, 프로젝트의 장기적인 지속 가능성은 유용성뿐만 아니라 사용자로부터 얻는 **신뢰**에 달려 있습니다. 이 신뢰를 유지하기 위해서는 강력한 보안 조치가 필수적입니다. 아래는 프로젝트의 보안 수준을 크게 향상시킬 수 있는 중요한 실천 사항들입니다. |
Contributor
There was a problem hiding this comment.
Original text doesn't have bold (**). Why did you add it?
Contributor
Committing suggested edits for a more user-friendly tone Co-authored-by: Roeniss Moon <roeniss2@gmail.com>
tomthorogood
temporarily deployed
to
Pages Preview
GitHub Actions
Inactive
tomthorogood
temporarily deployed
to
Pages Preview
GitHub Actions
Inactive
tomthorogood
temporarily deployed
to
Pages Preview
GitHub Actions
Inactive
Contributor
|
@eazyhozy are you still working on this? If not, I want to take this issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.
This PR adds a Korean translation of the Security Best Practices article.
Reference: https://opensource.guide/ko/security-best-practices-for-your-project/
Before (as-is)
After (to-be)