Step 1: 选择翻译提供商
该动作在统一的API表面下，使用Azure AI 翻译器、AWS 翻译和谷歌云翻译。每次运行选择一个提供者并使用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。优先通过aws-actions/configure-aws-credentials进行OIDC，这样就不会存储长期秘密——步骤会自动导出，导出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-translation谷歌云翻译
将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摘要。