Skip to content

docs(contributing): English-only language policy (#102) #106

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.

Sign up for GitHub

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

Merged
sgwannabe merged 1 commit into from
Apr 26, 2026
Merged

docs(contributing): English-only language policy (#102) #106

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,16 @@ Preview Forge introduces the **3-DD Methodology** (PreviewDD → SpecDD → Test
Contributions that strengthen any one of the three cycles, or that close
failure loops observed in real runs, are most welcome.

## Language

All issues, PRs, commits, code, and documentation in this repo are written in
**English**. This keeps the artifact archive uniform and accessible to
Comment on lines +9 to +10
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot Apr 26, 2026

Choose a reason for hiding this comment

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

P2 Badge Reconcile English-only rule with LESSON submission format

The new statement that all repo artifacts are written in English conflicts with the currently required LESSON workflow, which is explicitly defined as 문제 → 원인 → 해결 → 참조 in both the LESSON issue template (.github/ISSUE_TEMPLATE/lesson_contribution.yml:11,40-58) and this same guide (CONTRIBUTING.md:114-117). Contributors following the new rule will reasonably translate these fields to English, creating inconsistent submissions and avoidable triage friction for the LESSON pipeline.

Useful? React with 👍 / 👎.

non-Korean reviewers, and matches the standard already followed by every
shipped commit, PR body, CHANGELOG entry, and code comment. Korean prompts
during a Claude Code session are not a switch signal — agents should reply
in English by default. Make exceptions only for explicit, single-turn user
directives.
Comment on lines +9 to +15
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Apr 26, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

영어 전용 선언이 동일 문서 내 한국어 템플릿과 충돌합니다.

CONTRIBUTING.md에서 “모든 문서 영어”를 선언했지만, 같은 파일의 LESSON 포맷(문제/원인/해결/참조)은 한국어라 정책 해석이 모호해집니다. 정책 문구에 예외를 명시하거나 해당 템플릿 라벨을 영어로 맞춰 일관성을 확보해 주세요.

제안 수정안 (예: 템플릿 라벨 영어화) 
 ### N.M One-line summary
-- **문제**: …
-- **원인**: …
-- **해결**: …
-- **참조**: …
+- **Problem**: …
+- **Cause**: …
+- **Resolution**: …
+- **Reference**: …
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@CONTRIBUTING.md` around lines 9 - 15, The CONTRIBUTING.md currently enforces
"English-only" but contains the LESSON template labels "문제/원인/해결/참조", creating a
contradiction; update CONTRIBUTING.md to remove ambiguity by either (A)
converting the LESSON template labels to English (e.g.,
"Problem/Cause/Solution/References") wherever the LESSON format appears, or (B)
adding a short explicit exception clause under the English-only policy that
allows those specific template labels to remain in Korean; make the change in
the CONTRIBUTING.md LESSON template and any nearby policy sentence so the
document is consistent and unambiguous.


## Commit message convention

This repo uses **release-please** with [Conventional Commits](https://www.conventionalcommits.org/).
Expand Down
Loading