Step 1: 揀一個翻譯供應商
呢個動作喺一個統一嘅 API 表面下，配合Azure AI 翻譯器、AWS 翻譯同Google 雲端翻譯運作。 每次執行揀一個供應商用provider輸入——工作流程無論供應商邊個都一樣; 淨係資格唔同。 完整比較可以參考翻譯供應商。
Step 2: 加啲憑證同工作流程
將你供應商嘅憑證儲存為GitHub倉庫秘密，然後建立.github/workflows/translate.yml。 喺下面揀你嘅供應商，睇佢嘅具體設定——其他工作流程都係一樣。
Azure AI 翻譯器
Azure 係預設供應商，所以可以省略provider。 喺 Azure 門戶設置一個 Azure AI 翻譯器資源，然後儲存佢嘅憑證：
將佢哋儲存為倉庫秘密
TRANSLATOR_KEY— 資源嘅訂閱金鑰。TRANSLATOR_ENDPOINT— 區域端點 URL。TRANSLATOR_REGION— 資源嘅 Azure 區域。
加入工作流程
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-translationAWS 翻譯
將provider設為aws。 建議用 OIDC 經 aws-actions/configure-aws-credentials，咁就唔會儲存長期秘密——步驟會幫你匯出AWS_REGION。 如果想用靜態鍵，可以儲存：
將佢哋儲存為倉庫秘密
AWS_ACCESS_KEY_ID— 你嘅 AWS 存取密鑰 ID。AWS_SECRET_ACCESS_KEY— 你嘅AWS秘密存取金鑰。
一定需要一個區域——用awsRegion或者AWS_REGION環境變數設定。
加入工作流程
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-translationGoogle 雲端翻譯
將provider設為google。 用服務帳戶嘅 JSON 憑證或者 API 密鑰嚟認證——淨係提供一個：
將佢哋儲存為倉庫秘密
GCP_TRANSLATE_CREDENTIALS— 一個服務帳戶 JSON 鍵（以 JSON 字串形式）。GCP_TRANSLATE_API_KEY— 或者 Google Cloud API 金鑰。
如果冇咗資格，會推斷出一個可選googleProjectId。
加入工作流程
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-translationStep 3: 提交一個源資源檔案
資源檔案用Name.<sourceLocale>.<ext>慣例。 例如Greetings.en.resx跑完之後會變成Greetings.fr.resx、Greetings.de.resx等等。
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: 檢查輸出
工作流程完成後，動作會顯示三個輸出，你可以接駁成 PR 描述：summary-title、summary-details 同 has-new-translations。 佢仲會透過 core.summary 喺職位頁面寫入 Markdown 摘要。