Jiseoup/showmycodePublic
EN|KO
  • 코드
  • 커밋
  • 풀 리퀘스트
← 목록으로

Merge pull request #3 from Jiseoup/docs/add-i18n-convention

docs: add i18n branch and commit convention to project guidelines

JiseoupJISUB LIM · 2026년 3월 31일c95a282

변경된 파일2개+4 -2

변경된 파일

+4 -2 · 2개

@@ -28,8 +28,8 @@ Copy `.env.example` to `.env.local` and fill in:
This is an **open-source project** that accepts external contributions. All implementation decisions must follow open-source best practices:
-- **Branch strategy** — GitHub Flow. Work on feature branches (`feat/`, `fix/`, `chore/`, `refactor/`) and merge via PR to `main`.
-- **Commit messages** — Conventional Commits (`feat:`, `fix:`, `chore:`, `refactor:`, `docs:`, `test:`).
+- **Branch strategy** — GitHub Flow. Work on feature branches (`feat/`, `fix/`, `chore/`, `refactor/`, `docs/`, `test/`, `i18n/`) and merge via PR to `main`.
+- **Commit messages** — Conventional Commits (`feat:`, `fix:`, `chore:`, `refactor:`, `docs:`, `test:`, `i18n:`).
- **PR discipline** — Squash and merge. Every PR must pass CI (build + lint + test) and receive at least one review.
- **Code quality** — No PR without passing checks. Add tests for new features when a test framework is in place.
- **Documentation** — User-facing changes should update relevant docs. Keep CONTRIBUTING.md and Issue/PR templates current.
@@ -36,6 +36,7 @@ Create a branch from `main` using the following prefixes:
| `refactor/` | Code restructuring | `refactor/github-api` |
| `docs/` | Documentation only | `docs/setup-guide` |
| `test/` | Adding or updating tests | `test/api-route` |
+| `i18n/` | Internationalization (translations, locale) | `i18n/add-ja-locale` |
## Commit Messages
@@ -45,6 +46,7 @@ We follow [Conventional Commits](https://www.conventionalcommits.org/):
feat: add repository search to home page
fix: resolve syntax highlighting in dark mode
docs: update setup instructions for GitHub PAT
+i18n: add Japanese locale support
```
- Use the **imperative mood** ("add", not "added")