Boshlanish

Step 1: Tarjima provayderini tanlang

Harakat Azure AI Translator, AWS Translate va Google Bulut Tarjimasi bitta yagona API yuzasi ortida ishlaydi. Har bir ishga kirishda bitta provayderni tanlang, provider kirish bilan — ish jarayoni provayderdan qat'i nazar bir xil ishlaydi; faqat malakalar farq qiladi. To'liq taqqoslash uchun Tarjima xizmatlari qarang.

Step 2: Credentiallar va ish jarayonini qo'shish

Provayderingizning ma'lumotlarini GitHub ombori sirlari sifatida saqlang, so'ng .github/workflows/translate.yml yarating. Quyida provayderingizni tanlang — ish jarayonining qolgan qismi bir xil.

Azure AI Translator

Azure standart provayder bo'lgani uchun provider o'tkazib yuborilishi mumkin. Azure portalida Azure AI Translator resursini taqdim eting, so'ng uning ma'lumotlarini saqlang:

Bularni ombor sirlari sifatida saqlang

TRANSLATOR_KEY — resurs uchun obuna kaliti.
TRANSLATOR_ENDPOINT — mintaqaviy endpoint URL.
TRANSLATOR_REGION — resursning Azure mintaqasi.

Ish jarayonini qo'shing

name: translate

on:
  push:
    branches: [main]
    paths:
      - "src/**/*.en.resx"
      - "src/**/*.en.json"

permissions:
  contents: write
  pull-requests: write

jobs:
  translate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - id: translate
        uses: IEvangelist/resource-translator@v3
        with:
          provider: |
            azure:
              subscriptionKey: ${{ secrets.TRANSLATOR_KEY }}
              endpoint: ${{ secrets.TRANSLATOR_ENDPOINT }}
              region: ${{ secrets.TRANSLATOR_REGION }}
          sourceLocale: en
          toLocales: '["fr","de","es"]'
      - if: steps.translate.outputs.has-new-translations == 'true'
        uses: peter-evans/create-pull-request@v7
        with:
          title: ${{ steps.translate.outputs.summary-title }}
          body: ${{ steps.translate.outputs.summary-details }}
          branch: machine-translation

AWS Translate

provider aws qilib qo'ying. OIDCni aws-actions/configure-aws-credentials orqali afzal ko'ring, shunda uzoq umr ko'radigan sirlar saqlanmaydi — siz uchun qadam eksportlari AWS_REGION. Statik tugmalardan foydalanish uchun quyidagilarni saqlang:

Bularni ombor sirlari sifatida saqlang

AWS_ACCESS_KEY_ID — AWS kirish kaliti IDsi.
AWS_SECRET_ACCESS_KEY — sizning AWS maxfiy kirish kalitingiz.

Har doim hudud talab qilinadi — uni awsRegion yoki AWS_REGION muhit o'zgaruvchisi bilan belgilang.

Ish jarayonini qo'shing

name: translate

on:
  push:
    branches: [main]
    paths:
      - "src/**/*.en.resx"
      - "src/**/*.en.json"

permissions:
  id-token: write # for aws-actions/configure-aws-credentials (OIDC)
  contents: write
  pull-requests: write

jobs:
  translate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - uses: aws-actions/configure-aws-credentials@v4
        with:
          role-to-assume: arn:aws:iam::123456789012:role/gh-actions-translate
          aws-region: us-east-1
      - id: translate
        uses: IEvangelist/resource-translator@v3
        with:
          provider: |
            aws:
              region: us-east-1 # or rely on AWS_REGION from the step above
              formality: FORMAL
              brevity: true
          sourceLocale: en
          toLocales: '["fr","de","es"]'
      - if: steps.translate.outputs.has-new-translations == 'true'
        uses: peter-evans/create-pull-request@v7
        with:
          title: ${{ steps.translate.outputs.summary-title }}
          body: ${{ steps.translate.outputs.summary-details }}
          branch: machine-translation

Google Bulut Tarjimasi

provider google qilib qo'ying. Xizmat hisobidagi JSON ma'lumot ma'lumotlari yoki API kaliti bilan autentifikatsiya qiling — aynan bittasini taqdim eting:

Bularni ombor sirlari sifatida saqlang

GCP_TRANSLATE_CREDENTIALS — xizmat-hisob JSON kaliti (JSON satri sifatida).
GCP_TRANSLATE_API_KEY — yoki Google Cloud API kaliti.

Ixtiyoriy googleProjectId sertifikatdan chiqarib tashlanganda olinadi.

Ish jarayonini qo'shing

name: translate

on:
  push:
    branches: [main]
    paths:
      - "src/**/*.en.resx"
      - "src/**/*.en.json"

permissions:
  contents: write
  pull-requests: write

jobs:
  translate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - id: translate
        uses: IEvangelist/resource-translator@v3
        with:
          provider: |
            google:
              # Provide EITHER a service-account JSON credential...
              credentials: ${{ secrets.GCP_TRANSLATE_CREDENTIALS }}
              # ...OR an API key:
              # apiKey: ${{ secrets.GCP_TRANSLATE_API_KEY }}
              model: nmt
          sourceLocale: en
          toLocales: '["fr","de","es"]'
      - if: steps.translate.outputs.has-new-translations == 'true'
        uses: peter-evans/create-pull-request@v7
        with:
          title: ${{ steps.translate.outputs.summary-title }}
          body: ${{ steps.translate.outputs.summary-details }}
          branch: machine-translation

/* No JavaScript: the tablist can't switch panels, so hide it and reveal every provider's setup stacked. Keeps the page provider-neutral. */ [data-provider-tablist] { display: none !important; } [data-provider-panel][hidden] { display: block !important; }

Step 3: Manba resurs faylini commit qilish

Resurs fayllari Name.<sourceLocale>.<ext> konventsiyasidan foydalanadi. Masalan, Greetings.en.resx Greetings.fr.resx, Greetings.de.resx va hokazo bo'ladi.

Step 4: Let smart change detection protect your bill

changeDetection defaults to smart and stores a compact .github/resource-translator-state.json manifest in the repo. Commit that file so future runs can reuse stable translations, preserve manual target edits, and send only new, missing, changed, or settings-invalidated keys to the provider. If localized files already exist, run once with snapshotOnly: true to create the manifest without provider calls.

Step 5: Chiqishni tekshiring

Ish jarayoni tugagach, harakat uchta chiqishni PR tavsifiga ulash imkonini beradi: summary-title, summary-details va has-new-translations. Shuningdek, u ish sahifasiga Markdown qisqacha mazmunini core.summary orqali yozadi.

Tilingizni tanlang

Step 1: Tarjima provayderini tanlang

Step 2: Credentiallar va ish jarayonini qo'shish

Step 3: Manba resurs faylini commit qilish

Step 4: Let smart change detection protect your bill

Step 5: Chiqishni tekshiring

Keyingi qadamlar