Advanced

Internationalization (i18n)

Multilingual support in gh-please

Internationalization (i18n)

gh-please supports multilingual output with automatic system language detection.

Supported Languages

Korean (ko) - Full support
English (en) - Default and fallback

Automatic Language Detection

The CLI automatically detects your system language from environment variables:

LANG
LANGUAGE
LC_ALL

If any variable starts with ko, Korean messages are displayed. Otherwise, English is used.

Examples

Korean Output

LANG=ko_KR.UTF-8 gh please issue sub-issue list 123

Output:

🔍 상위 이슈 #123 가져오는 중...
✅ 성공적으로 하위 이슈를 조회했습니다.

상위 이슈 #123의 하위 이슈:
✅ #124 - 검증 로직 추가 (CLOSED)
🔵 #125 - 테스트 업데이트 (OPEN)

English Output

LANG=en_US.UTF-8 gh please issue sub-issue list 123

Output:

🔍 Getting parent issue #123...
✅ Successfully retrieved sub-issues.

Sub-issues of #123:
✅ #124 - Add validation (CLOSED)
🔵 #125 - Update tests (OPEN)

Command Messages

All user-facing messages are internationalized:

Success Messages

// Korean
msg.success.subIssueCreated(101, 100)
// "✅ 하위 이슈 #101이 성공적으로 생성되고 #100에 연결되었습니다."

// English
msg.success.subIssueCreated(101, 100)
// "✅ Sub-issue #101 created and linked to #100 successfully."

Error Messages

// Korean
msg.error.issueNotFound(123)
// "❌ 이슈 #123을 찾을 수 없습니다."

// English
msg.error.issueNotFound(123)
// "❌ Issue #123 not found."

Progress Messages

// Korean
msg.progress.gettingIssue(123)
// "🔍 이슈 #123 가져오는 중..."

// English
msg.progress.gettingIssue(123)
// "🔍 Getting issue #123..."

Implementation

Message Structure

Messages are organized by command group:

// src/lib/i18n.ts
export function getIssueMessages(lang: Language) {
  return {
    progress: {
      gettingParentIssue: (num: number) =>
        lang === 'ko'
          ? `🔍 상위 이슈 #${num} 가져오는 중...`
          : `🔍 Getting parent issue #${num}...`,
    },
    success: {
      subIssueCreated: (child: number, parent: number) =>
        lang === 'ko'
          ? `✅ 하위 이슈 #${child}이 성공적으로 생성되고 #${parent}에 연결되었습니다.`
          : `✅ Sub-issue #${child} created and linked to #${parent} successfully.`,
    },
    error: {
      issueNotFound: (num: number) =>
        lang === 'ko'
          ? `❌ 이슈 #${num}을 찾을 수 없습니다.`
          : `❌ Issue #${num} not found.`,
    },
  }
}

Usage in Commands

import { detectSystemLanguage, getIssueMessages } from '../../lib/i18n'

const lang = detectSystemLanguage()
const msg = getIssueMessages(lang)

console.log(msg.progress.gettingParentIssue(123))

Coverage

Internationalized

✅ All command output messages ✅ Success messages ✅ Error messages ✅ Progress indicators ✅ Help text and descriptions

Not Internationalized

⚠️ GitHub API URLs ⚠️ Git output ⚠️ JSON/XML structured output ⚠️ Technical error stack traces

Force Language

You can force a specific language by setting the environment variable:

# Force Korean
LANG=ko_KR.UTF-8 gh please issue sub-issue list 123

# Force English
LANG=en_US.UTF-8 gh please issue sub-issue list 123

# Also works with LANGUAGE
LANGUAGE=ko gh please issue sub-issue list 123

Adding New Languages

To add support for a new language:

Update the Language type in src/types.ts:

export type Language = 'ko' | 'en' | 'ja' // Add 'ja' for Japanese

Update language detection in src/lib/i18n.ts:

export function detectSystemLanguage(): Language {
  const lang = process.env.LANG || process.env.LANGUAGE || process.env.LC_ALL || 'en'
  if (lang.startsWith('ko'))
    return 'ko'
  if (lang.startsWith('ja'))
    return 'ja' // Add Japanese
  return 'en'
}

Add translations to message functions:

export function getIssueMessages(lang: Language) {
  return {
    progress: {
      gettingParentIssue: (num: number) => {
        if (lang === 'ko')
          return `🔍 상위 이슈 #${num} 가져오는 중...`
        if (lang === 'ja')
          return `🔍 親イシュー #${num} を取得中...`
        return `🔍 Getting parent issue #${num}...`
      },
    },
  }
}

Getting Started - Installation
Issue Management - Issue commands
PR Management - PR commands

Edit this pageorReport an issue

PR Review Workflow

Handle code review feedback efficiently with gh-please

API Limitations

GitHub API constraints and workarounds